4,661 件 ・ 関連度順
概要と使いどころ
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
日本語の概要は準備中です。原文の説明を表示しています。
Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...
日本語の概要は準備中です。原文の説明を表示しています。
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...
日本語の概要は準備中です。原文の説明を表示しています。
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
日本語の概要は準備中です。原文の説明を表示しています。
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...
日本語の概要は準備中です。原文の説明を表示しています。
Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that must follow AGENTS.md, POLICY.md, focused reproducer-first debugging, strict DRY/OOP boundaries, English comments, GOEXPERIMENT=runtimesecret test discipline, Makefile-driven validation, prompt-sync checks, and dirty-tree preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that needs worktree hygiene, the project documentation map, focused reproducer-first debugging, Makefile-driven validation, and evidence-backed closeout.
日本語の概要は準備中です。原文の説明を表示しています。
Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.
日本語の概要は準備中です。原文の説明を表示しています。
Provision hosting targets, configure domains/environments, integrate deployment pipeline, and verify staging access
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes codebase structure, data flow, module relationships, and key patterns to generate and maintain a living architecture document (ARCHITECTURE.md).
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
Deep code analysis covering security, performance, maintainability, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate concurrent analysis or implementation across independent domains. Use when a task can be decomposed into independent workstreams (e.g., via simultaneous tool calls or background processes) — spec writing, code review, security audit, feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.
日本語の概要は準備中です。原文の説明を表示しています。
AI Personal Assistant network skill. Use when: contacting another PA, coordinating with peer agents, scheduling meetings between owners, broadcasting messages, looking up contacts from the local PA directory, or performing any cross-PA task. Reads contact data from data/pa-directory.json in the workspace. Does NOT contain hardcoded contact data — each PA maintains their own directory file.
日本語の概要は準備中です。原文の説明を表示しています。
Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.
日本語の概要は準備中です。原文の説明を表示しています。
Report AI token usage and estimated costs. Use when: owner asks about costs today/yesterday/this week, per session, or per model. Shows main session, cron jobs, and subagents. Answers: 'how much did today cost?', 'how much was this session?', 'what was last week's spend?'
日本語の概要は準備中です。原文の説明を表示しています。
Build and run the owner's self-branding system in a structured way across LinkedIn, Substack, dev.to, X, profile rewrites, recurring series, and comment strategy. Use when the owner asks for positioning, a branding plan, profile updates, content drafts, a publishing sequence, comment ideas, or help maintaining a consistent public voice. Optimize for operator credibility: specific experience, defensible numbers, concrete artifacts, and category ownership.
日本語の概要は準備中です。原文の説明を表示しています。