agentleFS
Sign inStart free
NonetssNonetss/colofon/.agents/skills/stack/SKILL.md

stack

Skill0 starsChanged 13 days agoAGPL-3.0View on GitHub

Map and conventions of the colofon monorepo. Covers which workspace owns what (apps/frontend, apps/backend, apps/site, apps/gateway, packages/api, auth, config, content, cron, db, env, logger under the `@nonete/*` scope), path aliases (`@/` in apps, `#` subpath imports in packages), dependencies, root commands, env gotchas, tests and Docker (the hot-reloading dev stack, native dev, the dev PostgreSQL, the production-like compose.yml and the registry compose.prod.yml); which unit tests a new or changed procedure, helper, hook or component needs and how to write them (the fake database, fixtures, recipes per suite); frontend structure (features and slices, barrels, pages, app-surfaces and site-nav, Astro layouts, typography with the `Text` roles, `Hint` bubbles on icon-only controls, container queries, entity icons, charts with TanStack Charts, data tables with sortable and configurable columns, data fetching with TanStack Query over oRPC: query keys, invalidation, optimistic mutations, server-pushed refetches); how to find an existing component, hook, helper or procedure before writing new code; packages/api layering (feature files, procedure builders, errors, pagination and caller-chosen sort orders, event streams, HTTP methods and status codes, free-text search, versions); cron scheduling with `cronMeta`; and the TypeScript code style (no casts, no `??` chains or inline ternaries). Use before any code change in this repo, after implementing an endpoint or other rule-holding code to write its unit tests, before choosing or writing a React/UI component, hook, helper or procedure, to find where code lives, which convention applies and how to validate it.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.

Check your setup, free