Loading...
Loading...
Found 76 Skills
Analyze a GitHub codebase to create comprehensive architecture documentation including ASCII diagrams, component relationships, data flow, hosting infrastructure, and file structure assessment.
Ensures frontend and backend agree on API request/response shapes using Apidog MCP as the single source of truth. Replaces manual contracts.md files. Use when implementing or reviewing API endpoints and their consumers. Automatically loaded by team-lead, backend-dev, web-dev, mobile-dev, and reviewer.
Write Swift code for iOS/macOS following best practices. Use when developing with SwiftUI, UIKit, or Swift packages. Covers type safety, concurrency, and tooling.
Design scalable, reliable software systems. Use when planning new systems, major features, or architecture changes. Covers C4 diagrams, trade-off analysis, and system decomposition.
Manage project context effectively. Use when onboarding, context switching, or maintaining project knowledge. Covers context capture and sharing.
React Native Reanimated 4.x animation patterns. Use when adding animations, transitions, entering/exiting effects, or gesture-driven animations to React Native screens. Replaces Framer Motion for mobile.
Transforms research findings into executive-ready briefings. Automatically activated when user mentions 'executive', 'briefing', 'C-suite', 'board', 'leadership', or 'presentation'.
Context Store - Document management system for storing, querying, and retrieving documents across Claude Code sessions. Use this to maintain knowledge bases, share documents between agents. Whenever you encounter a <document id=*> in a session, use this skill to retrieve its content.
Best practices for Laravel queues including job structure, batching, chaining, middleware, retry strategies, and error handling.
Manage game assets with Kenney-ONLY approach. Search 36,000+ Kenney CC0 assets. If asset not found, ask user to find/generate manually. Ensure style consistency with flat/vector Kenney aesthetic. Auto-triggers on asset requests.
Improve code performance without changing behavior. Use when code fails latency/throughput requirements. Covers profiling, caching, and algorithmic optimization.
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.