菜单
Tracks Architecture Decision Records (ADRs) in docs/adrs/. Creates, lists, and updates ADRs following project conventions. TRIGGER when: user wants to record, review, or update an architectural decision.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Convert VTT meeting transcripts from meetings/incoming/ into structured markdown notes in meetings/
Check and align a repo's .claude/settings.json and CLAUDE.md with team conventions. Use when the user wants to standardize a repo, align conventions, check settings, or bootstrap Claude Code config in a new project.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Set up and maintain Gmail Multiple Inboxes with auto-discovered sender filters. Scans the user's Gmail to discover senders, suggests inbox categories, generates a Google Apps Script that creates labels and filters. Use this skill for: organizing Gmail, setting up multiple inboxes, managing Gmail labels and filters, categorizing email senders, updating inbox filters with new senders, or unsubscribing from noisy emails. Trigger phrases: "Gmail sections", "inbox categories", "email organization", "sender filters", "multiple inboxes", "clean up my inbox".
Morning review and prioritization of Things todos. Use this skill every morning, or whenever the user asks to review, triage, categorize, or prioritize their Things tasks. Also trigger when the user says things like 'what should I work on today', 'organize my todos', 'morning routine', or 'daily review'.
Generate or update distributed STRUCTURE.md index files across a repo to help LLMs orient quickly in project structure and to make large knowledge repositories easier to navigate and summarize.
| name | adr |
| description | Tracks Architecture Decision Records (ADRs) in docs/adrs/. Creates, lists, and updates ADRs following project conventions. TRIGGER when: user wants to record, review, or update an architectural decision. |
| argument-hint | [what you'd like to do] |
Manage Architecture Decision Records in docs/adrs/. Interpret $ARGUMENTS as natural language.
Ask the user for any missing information. You need at minimum: title, context, decision, and owner (@github-username).
If the decision is made → create docs/adrs/NNN-short-title.md with status Accepted.
If the decision is open → create docs/adrs/DRAFT-short-title.md with status Proposed.
Assign the next number by reading docs/adrs/index.md. Always update the index after creating a file.
Valid status transitions: Accepted, Deprecated, Superseded by ADR-NNN.
When promoting a Draft to Accepted: rename DRAFT-title.md → NNN-title.md and move the row from Drafts to Accepted in the index.
NNN-short-title.md — numbered, zero-padded to 3 digits, never reusedDRAFT-short-title.md — no number until accepteddocs/adrs/index.md — always keep in sync# ADR-NNN: Title
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-NNN
**Owner:** @github-username
## Context
What is the issue motivating this decision?
## Decision
What we decided.
## Alternatives Considered
What else was evaluated and why rejected.
## Consequences
What becomes easier or more difficult.