new-feature
Skill0 starsChanged 6 months agoMITView on GitHub
Feature development workflow. TRIGGER when: добавить функцию, add feature, новая фича, new feature, implement feature, новый эндпоинт, new endpoint, добавить страницу, add page, новый маршрут, new route, реализовать, implement, сделать так чтобы, make it so that, хочу чтобы, I want, нужна кнопка, need a button, добавить поле, add field, extend functionality. Contains: planning checklist, implementation steps, testing, deploy sequence.
- Sends data out
43 other projects use a version of this.
Adopted by
Most recently taken up by
- zyggy-org/zyggytheir own version, first seen Nov 16, 2026
- qivora-labs/agentinittheir own version, first seen Nov 15, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 15, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 15, 2026
- NemesLaszlo/claude-code-harnesstheir own version, first seen Nov 8, 2026
- michaelshimeles/rstacktheir own version, first seen Nov 1, 2026
Used with
Projects with it also use evidence-driven-testing, greploop-apps and 9 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
jaydubya818Skillgreploop-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 versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- jhd3197/ServerKit★ 1.8ksame name
- michaelshimeles/rstack★ 1.4ksame name
- michaelshimeles/skills★ 1.4ksame name
- fpindej/netrock★ 234same 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
33 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.
- CLAUDE.mdCLAUDE.md
- api-scaffoldSkill
- content-agentSkill
- db-healthSkill
- debug-serverSkill
- deploySkill
- git-workflowSkill
- log-monitorSkill
- max-apiSkill
- notebooklmSkill
- postgresqlSkill
- qa-agentSkill
- security-checkSkill
- ui-ux-pro-maxSkill
- web-proSkill
The file
Files
New Feature — Workflow
Step 1 — Understand the Task (before code)
Answer these questions:
- What exactly should the feature do? (user story)
- What data is needed? (new tables/fields in DB?)
- Where is it displayed? (which files are affected?)
- How to test manually?
Step 2 — Planning
Backend:
[ ] New route in routes/
[ ] Logic in a separate function (not in the route)
[ ] Input data validation
[ ] Error handling (try/catch)
Frontend:
[ ] HTML elements
[ ] JS event handler
[ ] fetch() to API
[ ] Show result / error to user
DB (if needed):
[ ] SQL migration (ALTER TABLE or CREATE TABLE)
[ ] Apply on server before deployStep 3 — Code Structure (Node.js/Express)
// routes/feature.js — thin route
router.post('/api/feature', async (req, res) => {
try {
const { param } = req.body;
if (!param) return res.status(400).json({ error: 'param required' });
const result = await featureService(param); // logic separate
res.json({ success: true, data: result });
} catch (err) {
console.error('feature error:', err);
res.status(500).json({ error: 'Internal error' });
}
});
// services/feature.js — business logic
async function featureService(param) {
const { rows } = await pool.query('SELECT ...', [param]);
return rows;
}Step 4 — Frontend Pattern
async function doFeature() {
try {
const resp = await fetch('/api/feature', {
method: 'POST',
headers: { 'Content-Type': 'application/json',
'Authorization': `Bearer ${token}` },
body: JSON.stringify({ param: value })
});
if (!resp.ok) throw new Error(await resp.text());
const data = await resp.json();
// show result
} catch (err) {
alert('Error: ' + err.message);
}
}Step 5 — Testing Before Deploy
# Locally (if available)
node server/index.js
curl -X POST http://localhost:3000/api/feature \
-H "Content-Type: application/json" \
-d '{"param": "test"}'Step 6 — Deploy
→ Use the deploy skill
Quality Checklist
- No hardcoded tokens/passwords
- All errors are handled (catch)
- Input data is validated
- Important events are logged (
console.logor logger) - API returns clear error messages
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.

