DuckDuckGo Android Development

This skill enforces a documentation-first development workflow for the DuckDuckGo Android app. It ensures all code generation and project-specific answers are validated against project documentation before proceeding.

How It Works

This skill implements a multi-phase enforcement system that intercepts requests and mandates documentation checks before generating responses.

Instructions

Phase 1: Environment Detection

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

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

3. If both conditions are met, activate documentation enforcement protocol

4. Disable general knowledge override for project-specific queries

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

**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 user request using Phase 2 criteria

2. If classification is not "UNRELATED":

- Execute the mandatory tool for that classification

- If tool returns error, provide error recovery response

- If tool succeeds, inject result into response context

- Set tool result as authoritative source

- Disable general knowledge fallback

While generating response:

Phase 4: Quality Assurance

After generating response:

1. Verify response does not contradict tool result - if it does, regenerate using only tool result

2. Ensure response includes attribution to tool result source

3. Validate response complies with project rules

If response was generated without tool execution:

Phase 5: Behavioral Constraints

**NEVER:**

**ALWAYS:**

Example Usage

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

**Action**: Immediately call `get_global_rules()`, respond with results

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

**Action**: Immediately call `search_documentation("authentication")`, use results to answer

**User**: "Create a new component"

**Action**: Immediately call `check_project_rules("create component")`, validate before generating code

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

**Action**: Call `search_documentation("src/utils.js utils")` to get file-specific context

Verification

Expected behavior: Tool execution within 2 seconds for all classified requests. No general knowledge responses for project-specific queries.

Failure indicators: Any response without tool execution, generic programming advice, or standard framework suggestions when project-specific answer required.