add-feature
Skill5 starsChanged 39 days agoMITView on GitHub
Use when the user asks to add a feature, implement functionality, or build something spanning database, API, and frontend. ALWAYS use for multi-layer feature work.
28 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Crypto69/claude-skillstheir own version, first seen Nov 16, 2026
- NVIDIA/nvcftheir own version, first seen Nov 15, 2026
- SHREESHMAN/lineupifytheir own version, first seen Nov 15, 2026
- subhashkhileri/agntreetheir own version, first seen Oct 25, 2026
- WhatIfWeDigDeeper/claude-code-courseratheir own version, first seen Oct 20, 2026
- NumericalEarth/Breeze.jltheir own version, first seen Oct 17, 2026
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- jpoindexter/theft-kit★ 158% same
Wrote their own version · 27
- fullstackhero/dotnet-starter-kit★ 6.9ksame name
- JamieMason/syncpack★ 2.1ksame name
- CliMA/Oceananigans.jl★ 1.4ksame name
- OpusGameLabs/game-creator★ 360same name
- microsoft/SqlScriptDOM★ 284same name
- NVIDIA/nvcf★ 268same name
- NumericalEarth/Breeze.jl★ 90same name
- nikandr-surkov/ai-saas-starter★ 16same name
- Azure/azure-functions-agents-runtime★ 13same name
- subhashkhileri/agntree★ 5same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- .agents/features/agents.mdAGENTS.md
- AGENTS.mdAGENTS.md
- add-endpointSkill
- add-entitySkill
- agent-browserSkill
- db-migrationSkill
- designSkill
- grill-meSkill
- local-docker-deploySkill
- mcp-builderSkill
- mintlifySkill
- playwright-e2e-testingSkill
- qadam-builderSkill
- ubiquitous-languageSkill
- versioningSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 1 is distinctive, and 11 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run the ubiquitous-language skill's overlap detection against .agents/features/ before proposing anything.
- Very specific: line 26
No edition gating, ever: All features are available to all users.
- Distinctive: line 33
Add a changeset (patch for a fix, minor for a new export)
- Very specific: line 37
Read .agents/features/<module-name>.md first (e.g.
- Very specific: line 39
Entity: follow the add-entity skill.
- Very specific: line 40
Register entity: add to getEntities() in database-connection.ts (REQUIRED — TypeORM doesn't auto-discover)
- Very specific: line 41
Migration: follow the db-migration skill — it is mandatory, not a reference.
- Very specific: line 43
Controller: follow the add-endpoint skill.
- Very specific: line 44
Project ownership: Add entitiesMustBeOwnedByCurrentProject hook if returning project-scoped data
- Very specific: line 50
Add to SystemJobName or WorkerJobType enum in shared
- Very specific: line 51
Add handler, register in app.ts via systemJobHandlers.registerJobHandler()
- Very specific: line 55
Read the design skill first — any new surface follows it
“Common” is measured: kept by at least 6 in 10 of the 26 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.
Files
Add Feature End-to-End
Implement feature described in $ARGUMENTS across the full stack.
Step 0: Check it does not already exist
Run the ubiquitous-language skill's overlap detection against .agents/features/ before
proposing anything. A feature that duplicates an existing one is the most expensive thing you
can ship here, and the registry exists to catch it in a minute.
Then answer, before writing code:
- Does a narrower skill own a step of this?
add-entity,add-endpointanddb-migrationare the authority on their own steps — this skill sequences them, it does not replace them. Read each one when you reach its step. - Project-scoped or platform-scoped? → every query filters by
projectIdorplatformIdaccordingly (.agents/rules/data-isolation.md). - Need a Permission? → add to the
Permissionenum inpackages/shared/src/lib/core/common/security/permission.ts. - Must work embedded? → check
EmbeddingStatein the frontend. - No edition gating, ever. All features are available to all users; there is no EE tree,
no paywall and no plan flag to hide behind (
.agents/rules/edition-safety.md).
Step 1: Shared Types (packages/shared)
- Define Zod schemas +
z.infertypes insrc/lib/{domain}/ - Export from
src/index.tsbarrel - Add a changeset (patch for a fix, minor for a new export)
Step 2: Server (packages/server/api)
Read .agents/features/<module-name>.md first (e.g. .agents/features/tables.md for the tables module).
- Entity: follow the
add-entityskill. Short version:EntitySchema+BaseColumnSchemaPart+ApIdSchema, seetables/table/table.entity.ts. - Register entity: add to
getEntities()indatabase-connection.ts(REQUIRED — TypeORM doesn't auto-discover) - Migration: follow the
db-migrationskill — it is mandatory, not a reference. - Service: Factory
(log: FastifyBaseLogger) => ({...})if logging needed, plain object otherwise. Seetables/table/table.service.ts. - Controller: follow the
add-endpointskill.FastifyPluginAsyncZod, route configs AFTER the controller,securityAccessrequired. Seetables/table/table.controller.ts. - Project ownership: Add
entitiesMustBeOwnedByCurrentProjecthook if returning project-scoped data - Module: register it in
app.tsalongside the existing modules — there is no CE/EE split to place it in - Side effects: Separate
*-side-effects.tsfile if mutations trigger events/webhooks
Step 3: Worker (if queued work needed)
- Add to
SystemJobNameorWorkerJobTypeenum in shared - Add handler, register in
app.tsviasystemJobHandlers.registerJobHandler()
Step 4: Frontend (packages/web)
- Read the
designskill first — any new surface follows it - Feature folder:
src/features/{feature}/api/,hooks/,components/ - API client: See
features/tables/api/tables-api.ts - Hooks: See
features/tables/hooks/table-hooks.ts - Route:
React.lazy()+ProjectRouterWrapper()+RoutePermissionGuard+SuspenseWrapper - Translations:
enplusru/uz/kkin the same PR (npm run check-i18nenforces parity) - Feature flags:
flagsHooks.useFlag()or<FlagGuard>
Step 5: Tests
- API test:
packages/server/api/test/integration/ce/{feature}.test.ts - Use
setupTestEnvironment()+createTestContext(app)
Step 6: Verify, then get it reviewed
npm run lint-dev
npm run typecheck # required once you touched packages/web — vite build does not type-check
npm run check-i18n # required once you touched translations
npm run test-apiThen delegate code-quality and app-sec per .agents/rules/agent-delegation.md, before
you report the feature done. A multi-layer feature is exactly the shape of change both
reviewers exist for.
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
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.

