aryaniyaps

Commit staged git changes with configurable message format and Co-authored-by trailer from .pi/auto-commit.json. Use when the user asks to commit, when /harness-auto or harness run completion requires a commit, or before any git commit — never use raw git commit -m.

Compile task-specific harness context using context-mode and graphify. Use for architecture questions, large codebase context before harness-plan or harness-run. NEVER use lean-ctx on harness paths.

Plan-phase Review Gate debate — pi-messenger threads, lane YAML, bus tools for parent orchestrator.

Structured user decisions via ask_user for harness setup, planning, and governance forks. Use with /harness-setup, /harness-plan, harness-auto plan phase, and when agents emit human_required.

Deprecated — use harness-review skill and /harness-review for the full post-run gate. This file remains as a pointer for older prompts.

Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages.

Bootstrap ls-lint filename rules for harness projects — seed naming.manifest.json, generate merge-safe .ls-lint.yml, and document bootstrap vs --force sync. Use during /harness-setup, when adding ls-lint to a repo, or when .ls-lint.yml is missing or out of date.

Orchestrate ultimate-pi harness phases with the native `subagent` tool (isolated `pi --mode json` subprocesses). Use for plan/execute/evaluate pipelines, L4 verification, optional planning-context, and debate prep.

Use only when explicitly invoked as lamina-design. Turn an incomplete product idea or brownfield change into a minimum sufficient product behavior graph: actors, entities, operations, workflows, rules, dependencies, decisions, persona perspectives, and distinct risks; then generate an implementation-ready contract.

Use only when explicitly invoked as lamina-init. Turn an incomplete product idea into usable business context and evidence-grounded personas, asking only high-leverage questions and labeling provisional assumptions for later product-graph design.

Product design workflows — domain contracts, implement brief, verify loop. Load via Read or Skill tool when /lamina-* workflows need it.

Use only when explicitly invoked as lamina. Route product design for developers building with AI — design, verify, or direct capability answers.

Use only when explicitly invoked as lamina-verify. Verify a live or brownfield product against its product graph: critical promises, reachable workflows, authority, invariants, state integrity, recovery, accessibility, and contract drift; emit evidence-backed fixes before merge.

Business context UX guidance. Use when bootstrapping Lamina for a project; answering business questions UX work needs; updating context after a pivot or scope change.

Lamina Problem Router — product design at the intersection of UX, product rules, and systems thinking.

Map prerequisite, data, lifecycle, and reachability dependencies between typed product-graph nodes, including explicit behavior when a dependency is unmet.

Custom blog writing agent that captures Aryan's writing style. Deep technical research, meme suggestions, engagement-focused structure. Talk freely — it handles research, structure, and drafting. Invoke as /blog-writer [topic or "brainstorm"].

Generate memes using the memegen.link API. Downloads the generated meme and saves it locally to the project for future proofing.

any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report

Operate the durable social content workflow through its compact Hermes tools.

Project conventions for agentic-uber — Go ADK console agent, real Uber Riders API, configurable LLM (OpenCode / OpenAI / Gemini), MarketplaceAdapter, action log, and confirmation gates.