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
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
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Commit what is already staged — runs the commit subagent in the background, following the ATLAS commit convention.
Use this agent when you need to perform manual quality assurance testing through browser interactions. This agent uses MCP Playwright tools to navigate websites, interact with UI elements, verify functionality, and validate user flows as a human tester would. Perfect for testing new features, regression testing, validating bug fixes, or exploring application behavior. Examples:\n\n<example>\nContext: The user has just implemented a new login feature and wants to test it.\nuser: "I've added a new login form, can you test if it works correctly?"\nassistant: "I'll use the qa-manual-tester agent to test the login functionality through the browser."\n<commentary>\nSince the user needs manual testing of a new feature, use the Task tool to launch the qa-manual-tester agent to interact with the browser and verify the login flow.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to verify that a bug fix is working properly.\nuser: "I fixed the issue where the submit button wasn't working on mobile view. Can you verify?"\nassistant: "Let me launch the qa-manual-tester agent to verify the submit button works correctly in mobile view."\n<commentary>\nThe user needs manual verification of a bug fix, so use the qa-manual-tester agent to test the specific functionality through browser interaction.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to perform regression testing after code changes.\nuser: "I've refactored the checkout flow. Please test that everything still works."\nassistant: "I'll use the qa-manual-tester agent to perform comprehensive testing of the checkout flow."\n<commentary>\nSince the user needs regression testing after refactoring, use the qa-manual-tester agent to manually test the entire checkout flow.\n</commentary>\n</example>
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
Initialize project context — understand the project, configure conventions, and set up project rules