DuckDuckGo Android Development

This skill enforces strict documentation-first development for the DuckDuckGo Android project using the doc-bot MCP server.

Environment Detection

Before responding to any request, check if:

If both conditions are met, activate documentation enforcement protocol. All responses MUST be grounded in project documentation accessed via MCP tools.

Request Classification

Classify every user request into one of these categories:

CODE_GENERATION

**Triggers**: write, create, implement, build, add, code, function, class, component, method, develop, generate, make, refactor, modify, update, fix, debug

**Required Action**: MUST call `check_project_rules` tool with task description before generating any code.

**Example**: "Create a new authentication component" → Call `check_project_rules("create authentication component")` first.

PROJECT_INQUIRY

**Triggers**: how, what, why, architecture, approach, pattern, feature, authentication, database, api, testing (in context of "this project", "this codebase", "here", "our project")

**Required Action**: MUST call `search_documentation` tool with extracted keywords before answering.

**Example**: "How does authentication work in this project?" → Call `search_documentation("authentication")` first.

DOCUMENTATION_DISCOVERY

**Triggers**: documentation, available, capabilities, help, rules, standards, what exists, docs, guide

**Required Action**: MUST call `get_global_rules` tool before responding.

**Example**: "What documentation is available?" → Call `get_global_rules()` first.

DOCUMENT_ACCESS

**Triggers**: read, show, get content, full document, complete, entire (when search results exist in context)

**Required Action**: Call `read_specific_document` tool with extracted filename.

**Example**: "Show me the full authentication.md file" → Call `read_specific_document("authentication.md")`.

File-Specific Queries

For queries about specific files (e.g., "working on src/utils.js"), use `search_documentation` with the file name and context keywords instead of a separate tool.

Execution Rules

Before Generating Any Response:

1. Classify the user's request

2. If classified as anything except UNRELATED:

- Execute the mandatory MCP tool for that classification

- Wait for tool result (timeout: 30s for searches, 15s for reads)

- If tool returns error, acknowledge and explain the error

3. Use ONLY the tool result to formulate your response

4. NEVER supplement with general programming knowledge

5. Always attribute information to the tool result source

Response Constraints:

Quality Assurance:

After generating a response:

If you generate a response without executing required tools, immediately correct yourself and regenerate using the tools.

Test Cases

Your responses to these inputs should immediately trigger tool calls:

Failure Indicators

These behaviors indicate incorrect implementation:

Example Interaction

**User**: "How should I implement user authentication?"

**Correct Response Flow**:

1. Classify as PROJECT_INQUIRY

2. Execute `search_documentation("user authentication implementation")`

3. Wait for results

4. Generate response based solely on documentation results

5. Attribute: "According to the project's authentication documentation..."

**Incorrect Response**: Providing generic Android authentication patterns without consulting project documentation.