anthropic-product-knowledge
This skill provides verified, current information about Anthropic's products, Claude API, Claude Code, and Claude.ai, by routing queries to official documentation and support resources rather than relying on potentially outdated training data. Use it whenever answering questions about product features, setup requirements, pricing, capabilities, or making provider comparisons to ensure accuracy and include proper source citations.
git clone --depth 1 https://github.com/syahiidkamil/Software-Engineer-AI-Agent-Atlas /tmp/anthropic-product-knowledge && cp -r /tmp/anthropic-product-knowledge/.claude/skills/anthropic-product-knowledge ~/.claude/skills/anthropic-product-knowledgeSKILL.md
# Anthropic Product Knowledge ## Core Principles 1. **Accuracy over guessing** - Check official docs when uncertain 2. **Distinguish products** - Claude.ai, Claude Code, and Claude API are separate products 3. **Source everything** - Always include official documentation URLs 4. **Right resource first** - Use the correct docs for each product (see routing below) --- ## Question Routing ### Claude API or Claude Code questions? → **Check the docs maps first**, then navigate to specific pages: - **Claude API & General:** https://docs.claude.com/en/docs_site_map.md - **Claude Code:** https://docs.anthropic.com/en/docs/claude-code/claude_code_docs_map.md ### Claude.ai questions? → **Browse the support page:** - **Claude.ai Help Center:** https://support.claude.com --- ## Response Workflow 1. **Identify the product** - API, Claude Code, or Claude.ai? 2. **Use the right resource** - Docs maps for API/Code, support page for Claude.ai 3. **Verify details** - Navigate to specific documentation pages 4. **Provide answer** - Include source link and specify which product 5. **If uncertain** - Direct user to relevant docs: "For the most current information, see [URL]" --- ## Quick Reference **Claude API:** - Documentation: https://docs.claude.com/en/api/overview - Docs Map: https://docs.claude.com/en/docs_site_map.md **Claude Code:** - Documentation: https://docs.claude.com/en/docs/claude-code/overview - Docs Map: https://docs.anthropic.com/en/docs/claude-code/claude_code_docs_map.md - npm Package: https://www.npmjs.com/package/@anthropic-ai/claude-code **Claude.ai:** - Support Center: https://support.claude.com - Getting Help: https://support.claude.com/en/articles/9015913-how-to-get-support **Other:** - Product News: https://www.anthropic.com/news - Enterprise Sales: https://www.anthropic.com/contact-sales
Activate ATLAS pattern recognition mode. Identify repeated patterns, extract essential characteristics, and create reusable abstractions from concrete examples.
Adversarially review something just built — presume it is broken and find where. Use after implementing a feature, finishing a build, or before shipping, or whenever ATLAS or Boss wants a hostile second opinion on a diff, a running app, or a whole codebase. Spawns clean-context reviewers with opposing lenses (correctness, security, empty-world) and reproduces every finding by running the target before believing it. Distinct from /code-review, which statically reads a diff and never runs the app.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Interview Boss about the project, then reason from first principles to design the ideal ATLAS operating identity/system-prompt for it — free to drop KISS/YAGNI/DRY/clean-architecture entirely when the project (and the LLM's own distribution) calls for a different mindset
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Code review a pull request