Claude Skills by dasha-ws

github.com/dasha-ws

13 skillsA× 130 installs0 views

ArchitectureAWork with the durable architecture of a target project in exactly one of three modes: document the current architecture of an existing project, design the initial architecture of a new product from a reviewed Product Spec, or, from a reviewed Feature Spec, design a substantial architecture change (first deciding whether one is needed, when the impact is unclear). Writes only .claude/skills/project-context/context/architecture.md. Substantive architecture work needs a PASS from the independent...developmentgoshellVotes: 0GitHub stars: 2
Build FeatureAImplement one work item in code: production code, its automated tests, and developer-level checks along the way. For substantial work it needs a current Tech Spec with an established /review-spec PASS; a real microchange may go without one. Not an independent quality gate: it never grants a /test-feature PASS, never reviews its own code and never calls a reviewer. Can be re-run to correct a concrete implementation-side finding of /test-feature, /review-code, /update-docs or /deploy-check. The...developmentgoshellVotes: 0GitHub stars: 2
Deploy CheckAThe final independent readiness gate before deployment or release, for one work item and one deployment target. Hands the accepted work to the independent security-reviewer and infrastructure-reviewer, aggregates their results and returns PASS, FAIL or BLOCKED — NO VERDICT. It checks readiness and never deploys, publishes or releases anything. It needs a reliably established current /update-docs PASS, and both reviewers are mandatory whenever it is run, microchanges included. Read-only, so it...developmentgoshellVotes: 0GitHub stars: 2
DeployAThe actual deployment step, for one deployment target at a time. After an applicable /deploy-check PASS it delivers exactly the checked version to the target through the project's established deployment mechanism (systemd is a supported branch, not the only one), verifies the result, and records the confirmed actual deployed state of that target in infrastructure.md. Also does read-only status and logs, and rollback by a known safe procedure. It is an executor, not a reviewer: it gives no rea...developmentgoshellVotes: 0GitHub stars: 2
Init ProjectAPrepare a target project for work with ai-dev-framework. Inspects the project's current state, then creates only the missing local project context, work folders and a short root CLAUDE.md, without inventing facts or overwriting anything. Entry point for new and existing projects; run it before /product-spec.developmentgodockerVotes: 0GitHub stars: 2
New Feature SpecACreate or substantially update the Feature Specification for one new feature, significant behaviour change or large fix in an existing product. Runs a short feature interview and writes .claude/work/<feature-name>/feature-spec.md from the installed template. Feature level only: no product-wide changes, no architecture, no Tech Spec. Run it after /init-project; after successful feature authoring the next mandatory step is /review-spec, while a product-level escape stops earlier and routes to /...developmentgodockerVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Product SpecACreate or substantially update the full Product Specification of a target project through a short product interview. Turns the product idea, the user's answers and the existing project context into agreed product requirements in .claude/product/product-spec.md, then syncs the short product.md context. Product level only: no architecture, no technical design. Run it after /init-project; the next mandatory step is /review-spec.developmentgodockerVotes: 0GitHub stars: 2
Review CodeAThe independent code-quality gate after a successful /test-feature, for one work item. Hands the already working implementation to the independent code-reviewer and returns PASS, FAIL or BLOCKED — NO VERDICT. It asks whether the code is technically sound, maintainable, appropriately simple and consistent with the approved technical design and project conventions. Read-only, so it never fixes code, and it is neither a second QA gate nor a security, architecture or deployment review. For substa...developmentrustgoVotes: 0GitHub stars: 2
Review SpecAThe mandatory PASS/FAIL quality gate for one specification: a Product Spec, a Feature Spec or a Tech Spec. Identifies the target, checks prerequisites, hands the spec to the matching independent reviewer-agent, validates its output and returns an unambiguous PASS or FAIL with concrete blocking findings. It never fixes or approves anything on its own. Its only write is its own row in the workflow ledger after a PASS. Run it after /product-spec, /new-feature-spec or /tech-spec, and again after ...developmentgoshellVotes: 0GitHub stars: 2
Tech SpecACreate or substantially update the Technical Specification for one implementation work item: how exactly the agreed, reviewed requirements are implemented inside the agreed architecture. Writes .claude/work/<work-item-name>/tech-spec.md from the installed template. Covers initial product implementation and feature implementation. Not a requirements or architecture document. The next mandatory step is /review-spec, and only after its PASS /build-feature.developmentgoshellVotes: 0GitHub stars: 2
Test FeatureAThe independent verification gate after /build-feature, for one work item. Orchestrates the reviewers that apply (qa-reviewer, product-reviewer and, for user-facing work, ux-reviewer), checks the already implemented behaviour against the approved requirements and returns PASS, FAIL or BLOCKED — NO VERDICT. Implementation is read-only here, so it never fixes code, tests or snapshots and never accepts "tests passed" from the builder as evidence. Works for substantial spec-driven work and for a ...developmentgoshellVotes: 0GitHub stars: 2
Update DocsAThe documentation synchronization gate after /review-code, for one work item. Works out what documentation or durable project context must change because of the implementation that was actually accepted, updates only that, then has the independent docs-reviewer confirm it, including when the answer is that no documentation changes are required. For substantial work, and for a microchange that went through /review-code, it needs a reliably established current /review-code PASS, and a microchan...developmentgoshellVotes: 0GitHub stars: 2
Project ContextARouter for this project's durable context files. Use it to decide which of product.md, architecture.md, development.md, infrastructure.md and ux-guide.md to read for the current task, and to read only what the task needs.developmentgotestingVotes: 0GitHub stars: 2