技術寫作

Utility scripts directory configuration (/scripts) for MetaSaver monorepos including setup automation, environment management, and cross-platform support. Includes 4 critical standards (setup scripts, cross-platform support, error handling, documentation). Use when creating or auditing /scripts directory with Node.js and shell utility scripts.

Gates expensive external research (perplexity deep_research) while allowing quick lookups. Enforces knowledge priority - local documentation and project patterns first, external research only when necessary. Permissive mode allows context7, local-rag, and quick perplexity searches. (project)

Use when writing background jobs or async operations - enforces thin job wrappers (3-5 lines) that delegate to models using _later/_now naming pattern

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Suggest wikilinks for current note using Flywheel MCP. Triggers on "suggest links", "link suggestions", "what should I link", "wikilink suggestions".

Works with PostgreSQL including queries, migrations, indexes, and performance tuning. Use when designing database schemas, writing SQL queries, optimizing performance, or managing PostgreSQL databases.

고고학 발굴조사보고서 고찰 자동 작성 파이프라인. "고찰 작성해줘" 한 번의 명령으로 완료된 보고서+논문+주변유적 보고서를 분석하여 문화재청 표준양식 고찰을 생성. 폴더1(주보고서), 폴더2(논문), 폴더3(비교유적)을 자동 분석. Use for automated archaeological excavation report discussion writing pipeline: analyzes main report + papers + comparison sites to generate discussion following Korean Cultural Heritage Administration standards. One command processes all folders.

Use for Phase 7 of Course OS - writing production-ready scripts adapted to content type including video scripts, voiceovers, presentation notes, and facilitation guides. Triggers on "/course-scripts", "write scripts", "video script", "presentation notes", or after completing Phase 6.

Service 层架构与前后端联调规范。Use when creating API services, writing Service classes, or handling backend integration. Triggers on: creating services, API calls, BaseService pattern, rewrites configuration, error handling.

Defines the standard 8-category taxonomy for classifying project files: Config, Tests, Docs, Scripts, Source Code, Data, AI Tooling, and Other. REFERENCE THIS SKILL whenever categorizing files, auditing project structure, or answering 'what types of files are here.' Apply these categories and patterns whether using the bundled script or manual analysis.

Guide for creating and updating README files following autonomous-bits development standards. Use this when asked to create or update README files, ensure documentation completeness, or review README quality.

Instrument services with Prometheus metrics and write PromQL queries. Guides HuleEdu naming conventions, metrics middleware setup, and business vs operational metrics. Integrates with Context7 for latest Prometheus documentation.

Automatically update repository documentation whenever code changes (add/edit/refactor) occur. Use when modifying source code, public APIs/contracts, rendering/interaction/data/compute logic, diagnostics, or build/release/CI flows so docs stay consistent without asking.

Write and maintain ADRs under docs/adrs when architecture decisions are made

Review text message conversations with a specified contact and send appropriate replies with cheerful tone and humor using Arlen's authentic writing style. This skill should be used when the user says "reply to [name]'s text", "respond to [name]", "text [name] back", or wants to send contextual replies to contacts. Automatically handles contact lookup and conversation review via subagent delegation. Integrates email skill writing style guide for authentic voice. Considers ALL messages received from contact since last reply (not just latest). TRIGGER PHRASES - "reply to", "respond to", "text back", "answer [name]'s message".

Create compelling demo narratives, flows, and presenter scripts for CustomGPT.ai Labs projects using existing demo links, project docs, and Innovation context.

Use when designing system architecture, creating design documents, planning technical architecture, or making high-level design decisions. Apply when user mentions system design, architecture, technical design, design docs, or asks to architect a solution. Use proactively when a feature requires architectural planning before implementation.

4-layer knowledge capture system for development sessions. Use when user says /mem (quick capture), /distill (extract patterns), /td (post-task retrospective with Before/After context), /improve (work on pending items), or /commit (atomic commits via TDG). Manages docs/learnings/, docs/knowledge-base/, and docs/retrospective/ directories.

Guidelines for writing effective tests in this project

Enrich a Github [DB] entry with GitHub API metadata (description, stars, language, cover image). Use when user wants to populate a GitHub repo entry with live metadata, enhance github entry, or add github info.