AI-powered content writing for tech, finance, and crypto. Blog posts, technical docs, whitepapers, market commentary. Research-backed, original, fast delivery.
Skills(SKILL.md)は、AIエージェント(Claude Code、Cursor、Codexなど)に特定の能力を追加するための設定ファイルです。
詳しく見る →AI-powered content writing for tech, finance, and crypto. Blog posts, technical docs, whitepapers, market commentary. Research-backed, original, fast delivery.
This skill helps you expand scattered ideas (a sentence, a few words, a vague thought) into **90+ point** social media posts.
Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017/745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.
You are helping the user create a Technical Design Document. This is Step 3 of the vibe-coding workflow.
vitepress-config-creator
adr-generator
architecture-doc-creator
changelog-generator
code-documentation-analyzer
code-of-conduct-generator
configuration-reference-generator
contributing-guide-creator
deprecation-notice-generator
docusaurus-config-setup
faq-generator
installation-guide-creator
mkdocs-config-generator
quickstart-guide-generator
release-notes-generator
runbook-creator
sdk-documentation-generator
troubleshooting-guide-creator
tutorial-outline-creator
ALWAYS use this when writing docs
Transforms detailed accessibility guidelines or technical documentation into a structured PowerPoint presentation, adhering to constraints on word count, slide limits, speaker notes, and visual suggestions.
>
Execute from requirement analysis to design document creation
Execute from requirement analysis to frontend design document creation
Create frontend work plan from design document and obtain plan approval
Create work plan from design document and obtain plan approval
Create PlantUML diagrams for UML and architecture documentation including sequence, class, component, deployment, state, activity, use case, and timing diagrams plus non-UML types like C4 models, ER diagrams, Gantt charts, mindmaps, network diagrams, and wireframes. Use when the user mentions PlantUML, needs UML diagrams, wants enterprise architecture diagrams, or requires precise UML notation or C4 model support.
Summarize academic papers with structured extraction of key elements
Search IEEE's 6M+ engineering and CS publications via the Xplore API
Document software architecture using ARCHITECTURE.md and docs/*.md files with Mermaid diagrams. Use proactively when ARCHITECTURE.md exists in project root, or invoke to create initial architecture documentation. Covers system design, data flows, component relationships, and code organization with references to key entry points and abstractions.
Document system architecture and technical design decisions for effective team communication and ...
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
Implement or tune AI opponent behavior
Comprehensive brownfield architecture analysis for existing codebases. Discovers structure, identifies patterns, assesses quality, calculates production readiness, and provides actionable recommendations. Use when analyzing existing codebases to understand architecture, assess quality, or prepare for modernization.
Creates comprehensive technical documentation from existing
Answer API and technical documentation questions. Use when a customer asks about API usage, code implementation, or integration details.
>
Create comprehensive technical documentation for code systems including data flow diagrams, architecture overviews, algorithm documentation, cheat sheets, and multi-file documentation sets. Use when documenting pipelines, algorithms, system architecture, data flow, multi-stage processes, similarity algorithms, or creating developer onboarding materials. Covers Mermaid diagrams, progressive disclosure, critical patterns, JSON schemas, Pydantic models, and print-friendly reference materials.
Provides overview of architecture documentation state.
bmad-planner
Transition from brainstorming to rough-draft skill
C4 model architecture visualization and documentation
Use after completing user-visible features, fixes, or behavior changes - NOT for internal docs (CLAUDE.md, DECISIONS.md, _tasks/)
Search and reference official Chromium documentation including design docs, APIs, and development guides
This skill should be used when creating or organizing working files in the .claude/ directory. It enforces consistent structure, naming conventions, and required cross-references for plans, architecture docs, examples, research, and analysis files.