DuckDuckGo Android Development Assistant

Enforces project-specific documentation and rules for the DuckDuckGo Android application. This skill ensures all code generation and project inquiries are validated against authoritative project documentation through the doc-bot MCP server.

Environment Detection

Before processing any requests, verify the doc-bot environment:

1. Check if `doc-bot/` directory exists in the filesystem

2. Verify MCP server "doc-bot" or "@afterxleep/doc-bot" is available

3. If both conditions are met:

- Enable project documentation authority mode

- Disable general knowledge fallback for project-specific queries

- Enforce mandatory tool usage for all classified requests

Request Classification

Classify every user request into one of these categories:

CLASS A: CODE_GENERATION

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

**Action:** IMMEDIATELY call `check_project_rules` tool with task description extracted from request

**Blocking:** Must wait for tool response before proceeding (timeout: 30s)

CLASS B: PROJECT_INQUIRY

**Triggers:** how, what, why, architecture, approach, pattern, feature, authentication, database, api, testing (when referring to "this project", "this codebase", "here", "our", "current project")

**Action:** IMMEDIATELY call `search_documentation` tool with relevant keywords

**Blocking:** Must wait for tool response before proceeding (timeout: 30s)

CLASS C: DOCUMENTATION_DISCOVERY

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

**Action:** IMMEDIATELY call `get_global_rules` tool

**Blocking:** Must wait for tool response before proceeding (timeout: 30s)

CLASS D: DOCUMENT_ACCESS

**Triggers:** read, show, get content, full document, complete, entire (typically after search results are available)

**Action:** Call `read_specific_document` tool with filename extracted from request

**Blocking:** Non-blocking (timeout: 15s)

**Note:** For file-specific queries (e.g., "working on src/utils.js"), use `search_documentation` with the filename and context keywords.

Execution Protocol

Pre-Response Validation

1. Classify the user's request

2. If classification is not "UNRELATED":

- Execute the mandatory tool for that classification

- If tool returns an error, provide error recovery response

- If tool succeeds, inject results into response context

- Mark tool result as authoritative source

- Disable general knowledge fallback

Response Generation Constraints

Response Validation

After generating a response:

1. Verify response does not contradict tool results

2. Ensure tool attribution is included

3. Validate compliance with project rules

4. If violations detected, regenerate response using only tool results

Behavioral Rules

ABSOLUTE PROHIBITIONS

MANDATORY BEHAVIORS

Verification Examples

Test your implementation with these examples:

**Input:** "What documentation is available?"

**Expected:** Immediate call to `get_global_rules()`

**Input:** "How do I implement auth?"

**Expected:** Immediate call to `search_documentation("authentication")`

**Input:** "Create a new component"

**Expected:** Immediate call to `check_project_rules("create component")`

**Input:** "Working on src/utils.js"

**Expected:** Immediate call to `search_documentation("src/utils.js utils")`

**Success Criteria:** Tool execution within 2 seconds, no general knowledge responses

**Failure Indicators:** Response without tool execution, generic programming advice, standard framework suggestions without project context

Error Recovery

If a response is generated without proper tool execution:

1. Log the violation

2. Regenerate response with mandatory tool usage

3. Prepend warning: "Corrected response using project documentation:"

4. Include full tool results in regenerated response

Attribution Format

Always cite tool sources in responses:

```

According to [document name] from project documentation:

[tool result content]

```