strategy-scaling-architecture
Architectural planning and scaling for spectre-build, covering GUI, server layers, multi-model support, and industrial pipeline orchestration.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
567 skills found
Architectural planning and scaling for spectre-build, covering GUI, server layers, multi-model support, and industrial pipeline orchestration.
Brainstorm differentiated product positioning strategies, identify key competitors, and craft compelling positioning statements with strategic rationale.
Enforce strict code quality, correctness, and Rust design patterns for the Turso database, prioritizing data integrity, performance, and maintainable, idiomatic code.
Safely execute, test, and verify commands discovered in documentation with real output capture, performance tracking, and git-aware safety protocols.
Nuxt framework disambiguation layer for optimizing project development, routing to the correct Nuxt pack, Vue guidance, or module-specific logic.
Analyze Kubernetes controller code to generate contract-compliant dependency graph artifacts for the Kamera coverage strategy.
Build complete UI screens by composing multiple uxscii components. Use when you need to create, scaffold, or build .uxm screens like login, dashboard, profile, settings, or checkout pages.
AI-driven GitHub Actions automation featuring swarm-based workflow orchestration, intelligent CI/CD pipeline management, and autonomous repository maintenance.
Generates comprehensive API references, user manuals, and architectural system documentation directly from your codebase and technical specifications.
Generates OpenAPI 3.0/3.1 specs from code (FastAPI, NestJS) or design-first schemas. Includes client SDK generation, mock server setup, and support for Swagger/ReDoc/Stoplight documentation workflows.
Implement the 'Engineering as Marketing' growth strategy: build free SEO-driven utility tools to drive organic traffic, capture leads, and convert visitors into customers without ad spend.
Identify and document Customer Problems (CP) from business context. Use when starting requirements engineering or when stakeholders describe solutions instead of problems. Step 1 of Problem-Based SRS methodology.