incremental-slices
Skill1 starsChanged 42 days agoMITView on GitHub
Deliver thin vertical slices that stay shippable. Use when building features across multiple layers or when the user wants incremental delivery.
In this repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- browser-verifySkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- debug-systematicSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- react-componentsSkill
- refactor-safeSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- ship-checklistSkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- spec-drivenSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use feature flags or safe defaults when releasing incomplete user journeys.
- Distinctive: line 18
Keep rollback simple (flag off / revert commit).
- Distinctive: line 32
Do not build the entire backend before any UI (or vice versa) unless constrained.
- Distinctive: line 33
Prefer end-to-end stubbed paths early over perfect abstractions.
- Distinctive: line 34
Keep each slice within a reviewable diff size when possible.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incremental Slices
Goal
Each slice is mergeable, testable, and optionally dark behind a flag.
Process
- Split the feature into vertical slices (UI→API→data or equivalent), not horizontal layers.
- Order by learning value and risk reduction.
- For each slice: implement → verify → commit.
- Use feature flags or safe defaults when releasing incomplete user journeys.
- Keep rollback simple (flag off / revert commit).
Slice Shape
Slice: <name>
User-visible outcome: ...
Touch points: ...
Test/verification: ...
Flag/default: ...Rules
- Do not build the entire backend before any UI (or vice versa) unless constrained.
- Prefer end-to-end stubbed paths early over perfect abstractions.
- Keep each slice within a reviewable diff size when possible.
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.