by secondsky88378361314fMIT227 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Guides creation of technical specifications for software projects, covering requirements, architecture, APIs, testing and risks.
Create comprehensive technical specifications for software projects.
POST /api/v1/resource Request: { "field": "value" } Response: { "id": "123", "field": "value" }
Source:secondsky/claude-skillsinplugins/technical-specification/skills/technical-specificationat commit8837836
License: MIT
Content belongs to its original authors. SourceWeft indexes it from a public repository.
secondsky
Guides automated vulnerability scanning of dependencies, code and containers with Trivy, Snyk, npm audit and Bandit.
secondsky
Guides web performance optimization via code splitting, lazy loading, caching, compression, and Core Web Vitals monitoring.
secondsky
Guides web performance audits using Core Web Vitals, Lighthouse, optimization strategies, and performance budgets.
secondsky
Reference knowledge base for building 3D web experiences with the Three.js library, covering ten core domains with code examples.
secondsky
Sets up Tailwind CSS v4 with shadcn/ui, Vite and React, including theming, dark mode and migration guidance.
secondsky
React Native and Expo best-practice rules covering list performance, animations, UI patterns, state, rendering and monorepo setup.
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.
# Technical Specification: [Feature Name]
## Metadata- **Status**: Draft | In Review | Approved- **Author**: [Name]- **Reviewers**: [Names]- **Last Updated**: [Date]
## Executive Summary[2-3 sentences: What problem does this solve? What's the proposed solution?]
## Background & Context- Current pain points- Why now?- Related work
## Goals### Primary Goals1. [Measurable goal]
### Non-Goals- [What this spec explicitly does NOT cover]
## Functional Requirements| ID | Requirement | Priority ||----|-------------|----------|| FR-1 | [Description] | P0 || FR-2 | [Description] | P1 |
## Non-Functional Requirements- **Performance**: Response time < 200ms- **Scalability**: Support 10K concurrent users- **Availability**: 99.9% uptime- **Security**: [Requirements]
## Technical Design
### Architecture[Diagram or description]
### API Design
### Database Schema```sqlCREATE TABLE resources ( id UUID PRIMARY KEY, field VARCHAR(255));
## Full Template
See [references/template.md](references/template.md) for a comprehensive copy-paste template including:- Complete metadata section- Success metrics tables- Architecture diagrams- Detailed API design sections- Security threat analysis- Monitoring & observability- Risk assessment matrix- Rollout and rollback plans- Dependencies tracking- Open questions section
## Best Practices
**Do:**- Include measurable acceptance criteria- Add architecture diagrams- Define explicit API contracts- Quantify performance targets- Document risks and mitigations- Get stakeholder review before implementation- Include security considerations- Define rollback procedures
**Don't:**- Use vague requirements ("fast", "scalable")- Skip non-functional requirements- Ignore security considerations- Leave alternatives unexplored- Omit testing strategy- Forget dependencies and risks