Claude Skills by semisemil

Initialize human-readable architecture memory from an existing codebase.

Update or seed opted-in architecture memory from Git.

Retrieve project decisions and operating constraints before planning or changing code; preserve durable context from conversation in opted-in architecture memory.

Use for Codex capability growth: review repeated manual work, shortlist automation candidates, check existing tools, and prepare skill/script/hook/Codex automation registration only after user approval.

Add the current Proofline project, or open, inspect, or stop the running Proofline dashboard server.

Create or revise a development Plan, clarifying rough ideas through dialogue. Use when the user requests development planning.

Use when the user asks to port, migrate, copy, or transplant an implementation while preserving behavior exactly or forbidding a rewrite. Keep the source authoritative and require approval for every deviation.

Think through a project change and carry it through the full Proofline development workflow.

Implement a ready Spec in the current session. Explicit invocation only.

Create, revise, complete, cancel, or supersede an implementation Spec under .proofline/specs without implementing it. Use for explicit Spec work, including invocation with an ID, path, or proposed contract.

Record and update concrete bugs, tasks, features, research, documentation, and maintenance in a project-local ledger. Use when the user asks to register or update project work, or when durable out-of-scope work should be preserved.

Apply Proofline's shared baseline rules for scope, authorization, evidence, language, compression, UI text, and code.

Use for structural refactors involving responsibility ownership, call paths, dependencies, or state/data flow. Verify that the intended structure is actually used.

Use when multiple requirements or stages risk losing approved scope or completion criteria. Not for ordinary low-risk work.

Explicit-only planning of useful independent parallel work for a ready Spec, without implementation or dispatch.

Select model and reasoning and launch a new local implementation session for a ready Spec. Explicit invocation only.

Review intent, outcome, and verification paths in a Spec, Plan, design, or stateful workflow using current evidence. Use only when the user explicitly invokes $tenet-me or $figure-it-out owns the explicit workflow.