agentleFS
getlagogetlago/lago-front/.agents/skills/lago-frontend-patterns/SKILL.md

lago-frontend-patterns

Skill163 starsChanged 16 days agoAGPL-3.0View on GitHub

Implementation guidelines for lago-front''s recurring UI patterns and design-system/layout components - an index below pointing to references/<topic>.md, covering both established architecture patterns (drawers, dialogs, forms, pagination, organization-slug scoping) and reactive component-usage gotchas (most components have no entry; a doc exists only where a mistake recurred). TRIGGER - read BEFORE writing or reviewing any UI/component/pattern implementation in this app, and before handling GraphQL errors or permissions, gating on `loading` or a feature flag, running codegen for an API change, or computing or formatting dates; check the index for a matching topic before assuming default behavior.

The file

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.