DuckDuckGo Android Development Assistant

This skill enforces project-specific documentation and coding standards for the DuckDuckGo Android application. It ensures all code generation and project inquiries are grounded in actual project documentation rather than general knowledge.

What This Skill Does

Instructions

PHASE 1: Environment Detection

Before processing any request:

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

2. Check if the `doc-bot` or `@afterxleep/doc-bot` MCP server is available

3. If both conditions are true:

- Activate documentation enforcement protocol

- Disable general knowledge fallback mode

- Set project documentation as authoritative source

PHASE 2: Request Classification

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**

**Special Case: File-Specific Queries**

PHASE 3: Execution Enforcement

Before generating any response:

1. Classify the user request using the matrix above

2. If classification is not "UNRELATED":

- Execute the mandatory tool(s) for that class

- Wait for tool results (respect timeout)

- If tool returns error: provide error recovery response

- If tool succeeds: inject results into response context

3. Set tool result as authoritative source

4. Disable general knowledge fallback

While generating response:

PHASE 4: Quality Assurance

After generating response:

1. Validate response does not contradict tool results

- If contradiction detected: regenerate using tool results only

2. Ensure response includes tool attribution

- If missing: append source attribution

3. Validate compliance with project rules returned by tools

If response was generated WITHOUT required tool execution:

PHASE 5: Behavioral Constraints

**ABSOLUTE PROHIBITIONS:**

**MANDATORY BEHAVIORS:**

Verification Tests

The agent MUST call tools immediately for these inputs:

| Input | Expected Tool Call |

|-------|-------------------|

| "What documentation is available?" | `get_global_rules()` |

| "How do I implement auth?" | `search_documentation("authentication")` |

| "Create a new component" | `check_project_rules("create component")` |

| "Working on src/utils.js" | `search_documentation("src/utils.js utils")` |

**Expected Behavior:** Tool execution within 2 seconds, no general knowledge responses.

**Failure Indicators:**

Examples

**Good:**

```

User: "How should I implement authentication?"

Agent: [Calls search_documentation("authentication")]

Agent: "Based on the project documentation, authentication in DuckDuckGo Android uses [specific pattern from docs]. Here's the approach from docs/auth.md: ..."

```

**Bad:**

```

User: "How should I implement authentication?"

Agent: "In Android, you typically use OAuth2 or JWT tokens..." [NO TOOL CALL - VIOLATION]

```

Important Notes