Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

spec-new

Étoiles1

Forks0

Mis à jour1 juillet 2026 à 01:30

Scaffold a new spec-driven feature in AlphaGalerkin — creates a specs/<feature>.spec.md from specs/TEMPLATE.spec.md and the mirrored src/ module + tests/ stubs. Use when starting any new PoC scenario, PDE operator, agent type, or module so the spec (data contract + acceptance criteria + MetricThreshold thresholds) is written before the code.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

ianshank

ianshank/AlphaGalerkin

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	spec-new
description	Scaffold a new spec-driven feature in AlphaGalerkin — creates a specs/<feature>.spec.md from specs/TEMPLATE.spec.md and the mirrored src/ module + tests/ stubs. Use when starting any new PoC scenario, PDE operator, agent type, or module so the spec (data contract + acceptance criteria + MetricThreshold thresholds) is written before the code.

spec-new — scaffold a spec-driven feature

AlphaGalerkin uses spec-driven development: write the contract before the code. This skill bootstraps that flow for a new feature named $FEATURE.

Steps

Copy the template: create specs/$FEATURE.spec.md from specs/TEMPLATE.spec.md. Fill in Context (link the CLAUDE.md Next-Steps row / ROI tier), User Story, Data Contract, Acceptance Criteria, and the Thresholds table.
Thresholds = existing type: express every pass/fail criterion as a src.poc.config.MetricThreshold(name, operator, value). Do not invent a new threshold schema — the feature's Pydantic config get_default_thresholds() is the single source of truth.
Mirror the layout: create the module under src/<pkg>/ and its test under tests/<pkg>/ (identical relative path). Follow the closest existing precedent (src/poc/scenarios/scaling_law.py + scaling_law_config.py for scenarios; src/pde/operators.py for PDE operators; src/agents/*.py for agents).
Config first: every tunable is a typed Field(default=…, <bounds>, description=…). Surface numerical-stability literals as named module constants.
AQA test: add a test asserting the config's get_default_thresholds() returns exactly the metrics/operators the spec's Thresholds table documents (spec ↔ config agreement).
Register the regression surface: add the feature's test command block to the Regression Surface table in CLAUDE.md.

Guardrails

Additive/backwards-compatible only: new files, new optional fields, new registry keys.
ruff + mypy --strict clean on the changed surface; tests to the 85% coverage gate.
Read specs/README.md for the full workflow.

Plus depuis ce dépôt

même dépôt

abstract-method-audit

ianshank/AlphaGalerkin

Audit a package's @abstractmethod and Protocol members for missing call sites — dead abstractions that every subclass implements but nothing invokes. Use before adding a new ABC/Protocol or reviewing a diff that touches one, to catch the F1-class defect (an abstract method spec'd in a docstring that never actually runs).

2026-07-101

coverage-gate

ianshank/AlphaGalerkin

Run the per-module coverage gate for an AlphaGalerkin package the way CI enforces it. Use before opening a PR to confirm a changed package still meets its --cov-fail-under threshold (branch coverage), matching the gates in .github/workflows/ci.yml and the CLAUDE.md Regression Surface.

2026-07-101

c4-architecture

ianshank/AlphaGalerkin

Standards for authoring C4 architecture documentation in Mermaid — Context, Container, and Component levels, dynamic views for key flows, and diagram hygiene rules. Use when creating or updating architecture docs — trigger phrases include "C4 diagram", "architecture doc", "document the architecture", "add a component diagram", "system context", or "sequence diagram for this flow".

2026-07-031

python-standards

ianshank/AlphaGalerkin

Prescriptive Python house standards covering Protocol-based dependency injection, Pydantic v2 configuration schemas, asyncio discipline, structlog structured logging, and strict typing/lint gates. Use when writing or reviewing any Python module, class, config, or async code — trigger phrases include "new module", "add a config", "wire a dependency", "add logging", "make this async", "fix mypy errors", or "does this meet standards".

2026-07-031

test-strategy

ianshank/AlphaGalerkin

House testing standards covering the test pyramid, per-module coverage gates, Hypothesis property-based testing, subprocess contract tests for CLIs, fixtures, deterministic tests, and marker-gated GPU/external tests. Use when writing tests, adding a module, reviewing test coverage, or deciding what kind of test a change needs — trigger phrases include "add tests", "write a test for", "coverage gate", "is this tested", "test this CLI", or "flaky test".

2026-07-031

new-pde-operator

ianshank/AlphaGalerkin

Add a new PDE operator to AlphaGalerkin end-to-end. Use when introducing a PDE family (e.g. a new elliptic/parabolic/vector operator) so it registers in the operator registry, the PDEType enum, the canonical PDE_TYPE_MAP, and every dependent Literal enum — following the documented checklist so scenarios auto-pick it up.

2026-07-011

name	spec-new
description	Scaffold a new spec-driven feature in AlphaGalerkin — creates a specs/<feature>.spec.md from specs/TEMPLATE.spec.md and the mirrored src/ module + tests/ stubs. Use when starting any new PoC scenario, PDE operator, agent type, or module so the spec (data contract + acceptance criteria + MetricThreshold thresholds) is written before the code.

spec-new — scaffold a spec-driven feature

AlphaGalerkin uses spec-driven development: write the contract before the code. This skill bootstraps that flow for a new feature named $FEATURE.

Steps

Copy the template: create specs/$FEATURE.spec.md from specs/TEMPLATE.spec.md. Fill in Context (link the CLAUDE.md Next-Steps row / ROI tier), User Story, Data Contract, Acceptance Criteria, and the Thresholds table.
Thresholds = existing type: express every pass/fail criterion as a src.poc.config.MetricThreshold(name, operator, value). Do not invent a new threshold schema — the feature's Pydantic config get_default_thresholds() is the single source of truth.
Mirror the layout: create the module under src/<pkg>/ and its test under tests/<pkg>/ (identical relative path). Follow the closest existing precedent (src/poc/scenarios/scaling_law.py + scaling_law_config.py for scenarios; src/pde/operators.py for PDE operators; src/agents/*.py for agents).
Config first: every tunable is a typed Field(default=…, <bounds>, description=…). Surface numerical-stability literals as named module constants.
AQA test: add a test asserting the config's get_default_thresholds() returns exactly the metrics/operators the spec's Thresholds table documents (spec ↔ config agreement).
Register the regression surface: add the feature's test command block to the Regression Surface table in CLAUDE.md.

Guardrails

Additive/backwards-compatible only: new files, new optional fields, new registry keys.
ruff + mypy --strict clean on the changed surface; tests to the 85% coverage gate.
Read specs/README.md for the full workflow.