Agistra

Use when drafting a bug or defect ticket, reviewing one someone else wrote, or deciding whether a reported problem is ready to file. Keeps what the reporter actually saw separate from what the agent later found out, so a reader can tell which lines are testimony and which are collected proof. Trigger phrases: 'file a bug', 'write up this defect', 'triage this report', 'is this ticket ready to file', 'what did the reporter actually see'.

The English summary is being prepared. Showing the original description.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

The English summary is being prepared. Showing the original description.

Use when: writing or reviewing cover letters, recruiter email replies, LinkedIn outreach, or interview follow-ups. Removes AI-template patterns and writes with a specific, confident, human voice.

The English summary is being prepared. Showing the original description.

Use immediately after RBR confirms a root cause, or after any confirmed finding from security-audit-lens, legacy-investigation-lens, a scan skill, or a Critical/Required code-review finding, before considering the finding complete. Checks whether the confirmed defect is one instance of a structurally identical pattern elsewhere in the same file family, workflow, or business-domain area, and folds in or explicitly defers every other instance found. Mandatory for Architect — not an optional lens the agent judges when to apply.

The English summary is being prepared. Showing the original description.

Use when: planner mode, planning mode, proposal, scope definition, estimate, timeline, how hard, feasibility, effort, how long, how big, client message, external communication, pricing, delivery confidence, commercial risk, or project delivery planning.

The English summary is being prepared. Showing the original description.

Use when: analysing a project's architecture, structure, and infrastructure health from the System perspective.

The English summary is being prepared. Showing the original description.

Use when: the agent captures a correction from the team lead, hits an unexpected error, discovers a capability gap, or finds a better practice. Logs to .learnings/ and promotes durable patterns to permanent project memory.

The English summary is being prepared. Showing the original description.

Review Codex/Claude agent skills, profile manifests, and skill-related deploy changes before they ship. Use when creating, editing, importing, installing, or reviewing SKILL.md files, agent manifests, optional third-party skills, or plugin skill bundles. Checks trigger quality, progressive disclosure, evidence gates, security, hallucination risk, validation, and deployment impact.

The English summary is being prepared. Showing the original description.

Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.

The English summary is being prepared. Showing the original description.

Use when: implement a scoped ticket, fix a bug, add tests, prepare a PR-ready code change, or reuse a standard builder workflow across software engineer agents.

The English summary is being prepared. Showing the original description.

Behavioral guardrails for implementation work. Reduces common LLM coding mistakes: overcomplication, silent assumption-picking, scope drift, and unverifiable success criteria. Load on Builder and software-engineer-mode.

The English summary is being prepared. Showing the original description.

Use when: remote team, delegate, delegated lane, delegated implementation, delegated QA, or non-sensitive ticket routing to the remote team's implementation lane.

The English summary is being prepared. Showing the original description.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

The English summary is being prepared. Showing the original description.

Use when: assessing how much context a deployed agent profile consumes before real work starts.

The English summary is being prepared. Showing the original description.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

The English summary is being prepared. Showing the original description.

Use when: analysing a project's user-facing health — discoverability, documentation, and product clarity.

The English summary is being prepared. Showing the original description.

Universal guardrails loaded by every agent. Defines Verify Before Reporting (VBR), Write-Ahead Log (WAL), and the security baseline. Always-on, role-independent.

The English summary is being prepared. Showing the original description.

Use when: assumptions audit, audit assumptions, check for hidden assumptions, plan/ticket has ambiguous scope edges, pre-flight before finalizing a ticket, unstated assumptions, or 'what am I assuming'. Surfaces unstated assumptions, ambiguous scope edges, and untested preconditions in a finished plan/ticket/ADR before it is handed to Builder. Optional pass — Architect judges when to apply it; not a mandatory gate on every ticket.

The English summary is being prepared. Showing the original description.

Use when: Tester needs UI state evidence for VBR, or Builder needs to verify an integration wire is observable end-to-end. Powered by agent-browser MCP — token-efficient browser automation (200–400 tokens/page).

The English summary is being prepared. Showing the original description.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

The English summary is being prepared. Showing the original description.

Writing skill for freelancers and independent consultants. Covers project proposals, bids, client emails, and scope summaries. Leads with the client's problem, not the consultant's background.

The English summary is being prepared. Showing the original description.

Activate for any ticket that touches a Supabase RPC, edge function, or TypeScript client function in src/lib/. Ensures both caller and callee are verified before state:ready-for-qa.

The English summary is being prepared. Showing the original description.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

The English summary is being prepared. Showing the original description.

Use when: Good night Team, EOD, Wrapping up, or end-of-day consolidation. Archives session context, promotes durable patterns, and compacts live agent memory files for the next session.

The English summary is being prepared. Showing the original description.