スキルを探す

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 a

日本語の概要は準備中です。原文の説明を表示しています。

Analytical methodology skill for intelligence-grade research. Covers cognitive security, logical fallacy detection, source epistemology, and probability discipline. Load when evaluating sources, building analytical assessments, or detecting manipulation in information.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: architecture mode, architect this, ADR, C4, PlantUML, system boundary, design decision, PRD gap, high ambiguity, multiple technical approaches, security architecture, data architecture, integration risk, implementability gap, story ticket, or epic ticket.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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 debug and reliability health — inline markers, logging hygiene, and error handling.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for any ticket that changes React components, user-facing flows, or UI state. Ensures all five observable UI states are verified before state:ready-for-qa.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: writing or reviewing a SKILL.md file, improving skill descriptions, organizing skill content, or needing guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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', or design review start. Produces ADRs and glossary as decisions settle. Do not use for settled designs — load architecture-mode instead.

日本語の概要は準備中です。原文の説明を表示しています。

Activate for any ticket that adds or changes a Supabase migration, environment variable, edge function deployment, or runtime configuration. Ensures infrastructure is live in the target QA environment before state:ready-for-qa.

日本語の概要は準備中です。原文の説明を表示しています。

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: Good morning Team, start-of-day briefing, or morning status request. Architect orchestrates; Builder, Tester, and Router return their sections as subagents.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Use when: reviewing or producing any external-facing prose — ADRs, proposals, GitHub comments, Telegram messages, cover letters, client drafts, or planner-mode wording. Removes AI-tell patterns and raises writing quality before output leaves the team.

日本語の概要は準備中です。原文の説明を表示しています。

Shared foundation for all human-voice writing skills. Load before any profession-specific skill. Contains: burstiness principle, perplexity principle, soul injection techniques, community-discovered AI patterns with sources, additional core patterns, banned AI vocabulary, and scoring rubric.

日本語の概要は準備中です。原文の説明を表示しています。