Loading...
Loading...
Found 200 Skills
Beeper Desktop CLI for chats, messages, search, and reminders.
Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.
This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.
Create comprehensive TypeScript documentation using JSDoc, TypeDoc, and multi-layered documentation patterns for different audiences. Includes API documentation, architectural decision records (ADRs), code examples, and framework-specific patterns for NestJS, Express, React, Angular, and Vue.
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
Use this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Use when writing ADRs, recording decisions, or evaluating options.
Map "Profit Growth × Financial Conditions (Financial Environment)" to the "Investment Clock" to determine the current quadrant, whether it has been rotating clockwise or counterclockwise recently, and the position difference compared to the previous cycle.
Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.
Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices). L2 Worker in ln-100-documents-pipeline.
Research best practices via MCP Ref/Context7/WebSearch and create documentation (guide/manual/ADR/research). Single research, multiple output types.
System architecture and technical design specialist. 🚨 TIER 2 SKILL - ON-DEMAND ACTIVATION 🚨 Use when user requests involve: - System architecture design and planning - Technical specifications and ADRs - Technology evaluation and selection - Scalability and performance planning - Integration architecture and API design - English: "design system", "architecture", "ADR", "tech stack", "scalability" - Swedish: "arkitektur", "systemdesign", "teknikval", "skalbarhet" Architecture Specialist (British female voice) provides: - System design and architecture patterns - Architecture Decision Records (ADRs) - Technology evaluation and trade-off analysis - Cloud and microservices architecture - Integration patterns and API design User confirmation optional but recommended for major architectural decisions.
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.