스킬 찾기

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'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

One-question-at-a-time design interrogation. Use when: 'grill me', 'interrogate this', 'one question at a time', 'brainstorm', 'let's brainstorm', 'let's discuss', 'lets discuss', 'discuss', 'walk me through', or design review start. Produces ADRs and glossary as decisions settle. Use for unsettled designs; for settled designs go straight to architecture-mode. When the design is unsettled and also has high ambiguity, several technical approaches, or security/data risk, load architecture-mode alongside.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: investigating a legacy, inherited, third-party-built, or otherwise newly-unfamiliar codebase before scoping a migration or major refactor. Formalizes a repeatable five-step investigation pass — entry-point census, business-rule classification, side-effect/idempotency cataloging, implicit-contract discovery, semantic-duplication detection — plus a canonical per-project Open Questions document. Requires checkable signals: ticket keywords or prior documentation gaps. Not a mandatory gate; reserved for entry-point-heavy work in code areas with no prior investigation record.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the team lead points Architect at a prior agistra.dev hub path and asks it to check for or perform additional migration — trigger phrasing such as 'migrate my data from <path>', 'check what didn't get migrated', 'did we miss anything from my old hub', or 'do a completeness pass on <path>'. Walks the prior hub's full directory tree read-only, diffs it against the fixed scripted migration scope plus any existing migration report, and asks the team lead one clear question at a time about anything a scripted migration would never have discovered. Never writes or copies anything itself — every confirmed item is delegated to the existing migration primitives. Do not use for the first-run scripted migration prompt during `npm run setup` — that is unrelated, already-automated flow this skill does not replace.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: Good morning Team, start-of-day briefing, or morning status request. Architect orchestrates; Builder, Tester, and Router return their sections as subagents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Context-survival and proactive-iteration extensions. Always-on. Covers Working Buffer Protocol, Compaction Recovery, Relentless Resourcefulness, and Self-Improvement Guardrails.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: analysing a project's test health — coverage, robustness, and CI integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: a general codebase assessment, pre-migration/pre-rewrite review, feasibility question about converting/migrating/rewriting a codebase (how hard, effort), or explicit security-focused request needs a structured, repeatable security audit pass covering hardcoded secrets, injection-prone constructs, auth/debug backdoors, insecure config defaults, and weak credential storage. Complements (does not replace) the built-in /security-review command. Not a mandatory gate on every ticket.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: Router bridges your team and the remote team across Telegram. Classifies inbound messages from the remote agent, dispatches Builder or Tester as subagents, composes replies, and posts outbound state-change notifications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: UI standards discovery, UI pattern research, UI audit, pre-handoff UI state coverage review, or when a business-specific child skill needs a stack-agnostic UI methodology to load first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Workflow-state classification vocabulary for inter-team relay. Maps inbound signals from the remote agent to a routing decision. Intentionally narrow — states and destinations only.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.