new-feature
Skill234 starsChanged 3 months agoMITView on GitHub
Scaffold a full-stack feature from entity to frontend page
42 other projects use a version of this.
Adopted by
Most recently taken up by
- qivora-labs/agentinittheir own version, first seen Nov 15, 2026
- NemesLaszlo/claude-code-harnesstheir own version, first seen Nov 8, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 7, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 7, 2026
- michaelshimeles/rstacktheir own version, first seen Nov 1, 2026
- qbicus/skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use evidence-driven-testing, greploop-apps and 10 more.
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.
jaydubya818Skillevidence-driven-testing
Capture observable runtime proof with video, screenshots, or measured output. Use when a change needs evidence beyond test reports.
Also in 6 projects that use this
- jaydubya818Skill
greploop-apps
Run greploop through @greptile-apps when the normal trigger rejects a large PR. Use only with the companion greploop skill.
Also in 4 projects that use this
VercelSkillbefore-and-after
Add existing screenshots or screen recordings to a GitHub pull request as a before/after or preview block. Use when a PR needs visual media attached to its description. Browser navigation and capture belong to agent-browser.
Also in 6 projects that use this
BboyfaroukSkillgreploop
Iteratively improves a PR until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes, re-triggers review, and repeats. Use when the user wants to fully optimize a PR against Greptile's code review standards.
Also in 6 projects that use this
u9401066Skillbug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
Also in 3 projects that use this
SvampenSkillinit-project
Generates a tailored .claude/project-config.md for the current project. Asks about project type, quality check commands, documentation paths, insight tags, and review strictness.
Also in 4 projects that use this
- +1 more from jaydubya818
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- jhd3197/ServerKit★ 1.8ksame name
- michaelshimeles/rstack★ 1.4ksame name
- michaelshimeles/skills★ 1.4ksame name
- X-isdoingreat/canvas-pilot★ 123same name
- AnjanJ/rails_error_dashboard★ 93same name
- dan-the-dev/xp-developer-skills★ 31same name
- Fadi88/one-man-startup★ 16same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- yerdaulet-damir/vibe-coding-rules★ 10same name
32 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 repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-aspire-depSkill
- add-background-jobSkill
- add-ci-areaSkill
- add-email-templateSkill
- add-env-varSkill
- add-options-classSkill
- add-permissionSkill
- add-rate-limitSkill
- address-reviewSkill
- add-testSkill
- backend-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- frontend-conventionsSkill
- gen-typesSkill
- infra-conventionsSkill
- init-verifySkill
- manage-file-storageSkill
- new-endpointSkill
- new-entitySkill
- new-pageSkill
- polish-uiSkill
- review-dependabotSkill
- review-designSkill
- review-prSkill
- security-conventionsSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Verify: dotnet build src/backend/MyProject.slnx - loop until green
- Distinctive: line 26
Write tests: component, API integration, validator
- Very specific: line 33
Add type alias to src/frontend/src/lib/types/index.ts
- Very specific: line 34
Create components in $lib/components/{feature}/ with barrel index.ts
- Very specific: line 35
Create page in routes/(app)/{feature}/
- Distinctive: line 36
Add i18n keys to the correct feature file in all locale directories
- Distinctive: line 37
Add sidebar navigation entry and command palette entry (both with permission if guarded)
- Distinctive: line 41
Always: If build/check fails, read the error, fix it, re-run.
“Common” is measured: kept by at least 6 in 10 of the 40 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
Creates a full-stack feature: backend entity through to frontend page.
Infers everything possible from the feature description. Asks only when genuinely ambiguous (multiple valid designs with different tradeoffs). Prefers conventions from existing features.
Steps
This chains entity -> service/API -> frontend. Commit atomically after each logical unit.
Backend - Entity (see /new-entity):
- Domain: entity + enums + error messages
- Infrastructure: EF config + DbSet + migration
- Verify:
dotnet build src/backend/MyProject.slnx- loop until green - Commit:
feat({feature}): add {Entity} entity and EF configuration
Backend - Service & API (see /new-endpoint):
- Application:
I{Feature}Service+ Input/Output DTOs - Infrastructure:
{Feature}Service(internal) + DI extension - WebApi: controller + request/response DTOs + mapper + validators + Program.cs wiring
- Write tests: component, API integration, validator
- Verify:
dotnet test src/backend/MyProject.slnx -c Release- loop until green - Commit:
feat({feature}): add {Feature} service and API endpoints
Frontend (see /new-page):
- Regenerate types:
cd src/frontend && pnpm run api:generate - Add type alias to
src/frontend/src/lib/types/index.ts - Create components in
$lib/components/{feature}/with barrelindex.ts - Create page in
routes/(app)/{feature}/ - Add i18n keys to the correct feature file in all locale directories
- Add sidebar navigation entry and command palette entry (both with permission if guarded)
- Verify:
cd src/frontend && pnpm run format && pnpm run lint && pnpm run check- loop until green - Commit:
feat({feature}): add {feature} frontend page
Always: If build/check fails, read the error, fix it, re-run. Never stop to report a fixable error.
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.