DuckDuckGo Android Development Assistant

This skill enforces strict adherence to project-specific documentation and rules for the DuckDuckGo Android application. It ensures all code generation and project inquiries leverage the doc-bot MCP server for authoritative information rather than relying on general knowledge.

What This Skill Does

Instructions for AI Agent

Phase 1: Environment Detection

On initialization, check if the DuckDuckGo Android project environment is active:

1. Verify filesystem contains `doc-bot/` directory

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

3. If both conditions met:

- Activate doc-bot enforcement protocol

- Set project documentation as authoritative source

- Disable general knowledge override for project-specific queries

Phase 2: Request Classification

Classify every user request using these patterns:

#### CLASS A: CODE_GENERATION

**Trigger keywords**: 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 extracted task description before generating any code.

**Blocking**: Cannot proceed without successful tool response (30s timeout)

#### CLASS B: PROJECT_INQUIRY

**Trigger keywords**: how, what, why, architecture, approach, pattern, feature, authentication, database, api, testing

**Context keywords**: this project, this codebase, here, our, current project

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

**Blocking**: Cannot proceed without successful tool response (30s timeout)

#### CLASS C: DOCUMENTATION_DISCOVERY

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

**Required action**: MUST call `get_global_rules` tool before answering.

**Blocking**: Cannot proceed without successful tool response (30s timeout)

#### CLASS D: DOCUMENT_ACCESS

**Trigger keywords**: read, show, get content, full document, complete, entire

**Context**: Previous search results exist

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

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

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

Phase 3: Execution Enforcement

Before generating any response:

1. **Classify the request** using the patterns above

2. **If classified as non-unrelated**:

- Execute the mandatory tool call for that classification

- Wait for tool result (within timeout)

- If tool returns ERROR, provide error recovery response

- Otherwise, inject tool result into response context

- Mark tool result as authoritative source

- Disable general knowledge fallback

3. **During response generation**:

- If attempting to use general knowledge when authoritative source exists, STOP and force use of authoritative source

- If code generation detected without project rules check, HALT and emit error

Phase 4: Quality Assurance

After generating a response:

1. **Validate response** does not contradict tool result

- If contradiction found, regenerate using only tool result

2. **Verify tool attribution** is included

- If missing, append attribution to tool result source

3. **Validate compliance** with project rules from tool response

**Failure Recovery**: If response was generated without required tool execution:

Phase 5: Behavioral Constraints

#### ABSOLUTE PROHIBITIONS (Never Do):

#### MANDATORY BEHAVIORS (Always Do):

Verification Examples

Test your implementation with these inputs (must call tools immediately):

1. **"What documentation is available?"** → Call `get_global_rules()`

2. **"How do I implement auth?"** → Call `search_documentation("authentication")`

3. **"Create a new component"** → Call `check_project_rules("create component")`

4. **"Working on src/utils.js"** → Call `search_documentation("src/utils.js utils")`

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

**Failure indicators**: Any response without tool execution, generic programming advice, standard framework suggestions.

Important Notes