作者 secondsky88378361314fMIT227 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫10 天前更新
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.
指導撰寫軟體專案技術規格書，涵蓋需求、架構、API、測試與風險。
Create comprehensive technical specifications for software projects.
POST /api/v1/resource Request: { "field": "value" } Response: { "id": "123", "field": "value" }
來源：secondsky/claude-skills位於plugins/technical-specification/skills/technical-specification提交8837836
授權條款： MIT
內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。
secondsky
指導使用 Trivy、Snyk、npm audit 與 Bandit 對相依套件、程式碼和容器進行自動化漏洞掃描。
secondsky
透過程式碼分割、延遲載入、快取、壓縮與 Core Web Vitals 監控來指導網頁效能最佳化。
secondsky
依據 Core Web Vitals、Lighthouse、最佳化策略與效能預算指導網頁效能稽核。
secondsky
用於以 Three.js 打造 3D 網頁體驗的參考知識庫，涵蓋十個核心領域並提供程式碼範例。
secondsky
設定 Tailwind CSS v4 與 shadcn/ui、Vite 和 React，涵蓋主題、深色模式與移轉指引。
secondsky
React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、UI 模式、狀態、渲染與 monorepo 設定。
anthropics
建立自成一體的互動式 HTML 遊樂場，包含控制項、即時預覽與可複製的提示詞輸出。
anthropics
透過 USB 偵測 M5Stack ESP32 開發板，燒錄 UIFlow 2.0 韌體並安裝 MicroPython 應用程式套件。
anthropics
指導迭代 Cardputer-Adv 的 MicroPython 應用程式套件：新增應用程式、透過 USB 序列埠推送檔案、查看日誌並執行 REPL 指令。
vercel-labs
依據從遠端來源取得的 Web Interface Guidelines 審查 UI 程式碼，並以 file:line 形式回報問題。
vercel-labs
React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、導覽、UI 模式、狀態與 monorepo 設定。
vercel-labs
Vercel 的 React 與 Next.js 效能指南，以 70 條規則的形式用於撰寫、審查與重構程式碼。
# 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