open-source
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODE_OF_CONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA", "DCO", "OpenSSF", "SBOM", "release automation", "npm publish", "make project open source", "prepare for open source" DO NOT USE FOR: Git workflow and branching - use git-workflow skill, Code quality and linting - use qa-expert agent, CI/CD pipeline design - use devops-expert agent
What this skill does
# Open Source Readiness - Core Knowledge
> **Deep Knowledge**: Use `mcp__documentation__fetch_docs` with technology: `git-workflow` for Git-specific documentation.
## When NOT to Use This Skill
This skill focuses on open source project setup and compliance. Do NOT use for:
- **Git commands and branching** - Use `git-workflow` skill
- **Code quality and static analysis** - Use `qa-expert` agent
- **CI/CD pipeline architecture** - Use `devops-expert` agent
- **Package development (library code)** - Use language-specific skills
## Essential Files Checklist
| File | Purpose | Priority |
|------|---------|----------|
| `LICENSE` | Legal terms for use and distribution | Required |
| `README.md` | Project overview, install, usage, badges | Required |
| `CONTRIBUTING.md` | How to contribute (setup, PR process, style) | Required |
| `CODE_OF_CONDUCT.md` | Community behavior expectations | Required |
| `SECURITY.md` | Responsible disclosure process | Required |
| `CHANGELOG.md` | Version history (Keep a Changelog) | Recommended |
| `GOVERNANCE.md` | Decision-making process | Recommended |
| `.github/CODEOWNERS` | Auto-assign reviewers by path | Recommended |
| `.github/FUNDING.yml` | Sponsorship links | Optional |
| `CITATION.cff` | Academic citation metadata | Optional |
| `NOTICE` | Third-party attributions (Apache 2.0) | Conditional |
## Quick Reference Guides
| Topic | Guide | Covers |
|-------|-------|--------|
| Licensing | [licensing.md](quick-ref/licensing.md) | License selection, SPDX, CLA/DCO, compatibility |
| Documentation | [documentation.md](quick-ref/documentation.md) | README, CONTRIBUTING, CHANGELOG, ADR templates |
| Community and Governance | [community-governance.md](quick-ref/community-governance.md) | Governance models, maintainer path, communication |
| Repository Setup | [repository-setup.md](quick-ref/repository-setup.md) | .github/, templates, CODEOWNERS, branch rules |
| CI/CD and Automation | [ci-cd-automation.md](quick-ref/ci-cd-automation.md) | GitHub Actions, releases, dependency updates |
| Compliance | [security-compliance.md](quick-ref/security-compliance.md) | OpenSSF Scorecard, SBOM, supply chain |
| Legal and Packaging | [legal-packaging.md](quick-ref/legal-packaging.md) | License headers, NOTICE, publishing, signing |
| Metrics and Inclusivity | [metrics-inclusivity.md](quick-ref/metrics-inclusivity.md) | CHAOSS metrics, inclusive language, badges |
## Decision Flowchart
```
Project needs open source setup?
- Just starting? -> Run full Tier 1 setup
- Choose license -> licensing.md
- Create docs -> documentation.md
- Setup repo -> repository-setup.md
- Add CI -> ci-cd-automation.md
- Already has basics? -> Run audit, fill gaps
- Missing compliance files? -> security-compliance.md
- No community docs? -> community-governance.md
- No release process? -> ci-cd-automation.md
- Publishing a package? -> legal-packaging.md
- Growing community? -> community-governance.md + metrics-inclusivity.md
- Compliance audit? -> security-compliance.md + legal-packaging.md
```
## License Quick Decision
| If you want... | Choose |
|-----------------|--------|
| Maximum freedom, simple | MIT |
| Patent protection included | Apache 2.0 |
| Copyleft (derivatives must be open) | GPL v3 |
| Copyleft for libraries only | LGPL v3 |
| File-level copyleft (compromise) | MPL 2.0 |
| Network copyleft (SaaS must share) | AGPL v3 |
| Public domain equivalent | Unlicense or 0BSD |
## Common Anti-Patterns
| Anti-Pattern | Why It Is Bad | Best Practice |
|--------------|---------------|---------------|
| No LICENSE file | Code is NOT open source without one | Always include LICENSE |
| LICENSE in README only | Not legally clear | Separate LICENSE file |
| No CONTRIBUTING.md | Contributors do not know how to help | Clear contribution guide |
| No CODE_OF_CONDUCT | Unwelcoming community signal | Adopt Contributor Covenant |
| Hardcoded secrets | Credential exposure risk | Use environment variables |
| No .gitignore | Accidental binary commits | Comprehensive .gitignore |
| No CI pipeline | Untested contributions | GitHub Actions CI |
| No issue templates | Low-quality bug reports | Structured YAML templates |
| Manual releases | Error-prone, inconsistent | Automated release pipeline |
| No SECURITY.md | Issues reported publicly | Private disclosure process |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.