Enforces project-specific documentation and rules for DuckDuckGo Android app development. Ensures all code generation and project inquiries use authoritative project documentation via MCP tools rather than general knowledge.
This skill enforces project-specific documentation and coding standards for the DuckDuckGo Android app. It ensures that all code generation, architectural decisions, and project inquiries are based on authoritative project documentation rather than general knowledge.
When working on the DuckDuckGo Android codebase, this skill activates a strict documentation-first protocol. It classifies all requests and mandates the use of MCP documentation tools before generating any responses. This prevents generic advice and ensures all recommendations align with project-specific patterns, architecture, and standards.
Check if you are working within the DuckDuckGo Android project:
If these conditions are met, activate the documentation enforcement protocol and disable general knowledge fallback.
Classify every user request into one of these categories:
**CLASS A: CODE_GENERATION**
**CLASS B: PROJECT_INQUIRY**
**CLASS C: DOCUMENTATION_DISCOVERY**
**CLASS D: DOCUMENT_ACCESS**
**Note**: For file-specific queries (e.g., "working on src/utils.js"), use `search_documentation` with the file name and context keywords.
**Before generating any response:**
1. Classify the user's request
2. Execute the mandatory tool call for that classification
3. Wait for the tool result (do not proceed on timeout or error)
4. Use ONLY the tool result as the authoritative source
5. Disable general knowledge fallback completely
**During response generation:**
**After generating a response:**
**NEVER:**
**ALWAYS:**
**Example 1: Code Generation Request**
```
User: "Create a new authentication component"
Action: MUST call check_project_rules("create authentication component")
Response: Based on project documentation, [use tool results to guide implementation]
```
**Example 2: Project Inquiry**
```
User: "How does authentication work in this project?"
Action: MUST call search_documentation("authentication")
Response: According to the project documentation, [provide documentation-based answer]
```
**Example 3: Documentation Discovery**
```
User: "What documentation is available?"
Action: MUST call get_global_rules()
Response: [List available documentation from tool result]
```
**Example 4: File-Specific Query**
```
User: "I'm working on src/utils.js, what should I know?"
Action: MUST call search_documentation("src/utils.js utils")
Response: [Provide documentation specific to that file and utilities]
```
Test that the skill is working by checking:
**Failure indicators:**
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/duckduckgo-android-development-rvny1z/raw