All authors
Claude Skills by teklabsdigital
github.com/teklabsdigital13 skills0 installs21 views
- AdoptUse when an existing project that was not built with X2 must be migrated to run under it, with documentation sprawl to dissolve, stories to harvest at epic altitude, an as-built design to baseline, and existing enforcement to map and arm. Runs the migration on a dedicated branch with three human gates. Do not use for a new project (that is seed), and do not use it to redesign the product or refactor code beyond what arming the enforcement requires.Votes: 0GitHub stars: 15
- DecomposeUse after the repo is seeded to run the D-000 five-lens decomposition, record persistent schema decisions, define slice one, and start the deltas file. Also use when a stays-ahead decision (decomposition, schema) must be revisited. Do not use for per-slice implementation decisions; those are D-0xx record-gaps raised during implement.Votes: 0GitHub stars: 15
- Derive TestsUse only after the lock (gate 2b) is on record for the slice portion, to derive the fidelity ledger and acceptance scenarios from the locked prototype. Triggers when a portion is newly locked or re-locked. Never use before the lock, and never use it to hand-author prototype-fidelity test cases from prose.Votes: 0GitHub stars: 15
- DesignUse when D-000 exists and the whole-product prototype does not, to run Claude Design in its own context and produce the prototype and design system. Also use when a later slice exposes a design gap that needs a spine revision. Requests gate 2a (prototype approved at Claude Design). Never run in the builder's context, and never used to author tests, acceptance criteria, or application code.Votes: 0GitHub stars: 15
- ExtractUse when an X2 project completes (or reaches a major milestone) to run the extraction loop, the quality feedback that folds the project's evidence back into the method. Reads the turn ledger and decision records, computes the metric and the per-decision churn table, distils sanitized candidates, confirmations, and negative-space nominations, and holds everything for a rulings pass. Do not use mid-slice (that is the normal intake flow), and never let raw project material cross into the public ...Votes: 0GitHub stars: 15
- HelpUse when someone asks what an X2 skill does, which skill to run next, how the gates work, or where an artifact lives. A quick in-flight reference; for the method's rationale, read X2.md at the method repo root.Votes: 0GitHub stars: 15
- ImplementUse when the slice portion is locked and its derived tests exist, to build all of the locked portion to green autonomously. Triggers at implement start and on every re-entry after a human turn. Do not use to declare green (slice-exit does that), and do not use it for an unexplained runtime defect (problem-solve).Votes: 0GitHub stars: 15
- KernelUse to change the claims catalog (add, amend, retire a claim, cut a catalog pass), to manage editions (add, retire, recompose), to measure an edition's conformance honestly (plant, prove, audit, lower a row), to clear accumulated decisions with the owner, or to check that the whole kernel is still coherent. Also use when a claim or edition change may have left counts, scope or statements in the documentation stale. Do not use it to seed a project from an edition; that is seed's job.Votes: 0GitHub stars: 15
- LockUse when the prototype is approved at Claude Design (gate 2a) and a slice's portion must be copied down into the repo and locked. Also use when a spine revision touches an already-locked portion and it must be re-locked. Requests gate 2b (the lock). Do not use before gate 2a, and do not derive tests here; that is derive-tests, after the lock.Votes: 0GitHub stars: 15
- Problem SolveUse when the product misbehaves at runtime and the cause is unknown, especially when reproducing needs the human's device, eyes, or account. Do not use for a red test with an evident cause (stay in the implement loop) or for green-but-wrong against the locked prototype (that is an adjudication turn; the fix goes in the decision file).Votes: 0GitHub stars: 15
- SeedUse immediately after gate 1 (stories approved) to settle which kernel edition the project is built on, create the project repo from it, and make the method durable inside it. Also use when an existing X2 project is missing its CLAUDE.md standing constraints or its turn ledger. Do not use before stories are approved, and never use it to modify the kernel itself.Votes: 0GitHub stars: 15
- Slice ExitUse when the builder believes the slice is green, to produce the slice-exit report that is the definition of green. Triggers before any green declaration and at slice close. Green is declared by the report and ratified only after intake audits it. Never declare a slice green in prose, and never skip a section because it is inconvenient.Votes: 0GitHub stars: 15
- StoriesUse when starting an X2 project, when the problem domain has no approved epic story set, or when new scope needs stories added to an existing set. Runs problem discovery and produces epic-level stories, then requests gate 1 (stories approved). Do not use to author acceptance criteria or a requirements document, and do not use for anything downstream of gate 1.Votes: 0GitHub stars: 15