What Context Needed

An AI skill that analyzes coding tasks and determines what context information an AI assistant needs to provide accurate help, generating specific questions and file requests that gather the minimum necessary context for effective assistance.

What Is This?

Overview

This skill evaluates a coding task and identifies exactly what context an AI assistant needs. It generates targeted requirements: specific files to share, configuration details, and error messages to include. This helps developers provide the right information up front.

Who Should Use This

Useful for developers who want efficient AI assistance without lengthy back and forth, teams creating prompt templates, and AI tool builders designing context gathering workflows.

Why Use It?

Problems It Solves

Developers often provide too little or too much context when asking for AI help. Too little leads to generic answers. Too much buries relevant information. This skill identifies the minimum effective context set for each type of request.

Core Highlights

• Task Analysis determines the type of coding task and its context requirements
• Targeted Questions generates specific questions rather than generic follow-ups
• File Identification names the exact files an AI assistant would need to see
• Priority Ranking orders context items by importance for the specific task
• Minimal Context requests only what is necessary to avoid information overload

How to Use It?

Basic Usage

Describe a coding task and receive a structured list of context requirements.

## Context Requirements for: "Fix the login form validation"

### Essential (must have):
1. The login form component file (e.g., LoginForm.tsx)
2. Current validation logic or schema file
3. The specific error or incorrect behavior observed
4. Browser console errors if any

### Helpful (improves answer quality):
5. Form library used (React Hook Form, Formik, native)
6. Validation library (Zod, Yup, custom)
7. API endpoint the form submits to

### Optional (for edge cases):
8. Test files for the login form
9. Authentication flow documentation

Real-World Examples

Complex Debugging Context

A developer asked for help with a production memory leak. The skill identified that generic advice would be useless without specific context and generated a prioritized list for diagnosis.

task_type: debugging
complexity: high

required_context:
  - item: "Memory usage graph or metrics over time"
    reason: "Confirms leak pattern vs normal growth"
    priority: 1
  - item: "Heap snapshot or profile output"
    reason: "Identifies which objects are retained"
    priority: 2
  - item: "Node.js version and runtime flags"
    reason: "Known memory issues in specific versions"
    priority: 3
  - item: "Code handling long-lived connections or caches"
    reason: "Common leak sources in Node.js servers"
    priority: 4
  - item: "Package.json dependencies list"
    reason: "Known leaky packages can be identified"
    priority: 5

Advanced Tips

Use this skill at the start of every AI session to front-load context. Create saved templates for recurring task types. Combine with project documentation links for AI self-service.

When to Use It?

Use Cases

• Bug Reports determine what information makes a bug report actionable
• Code Review Requests identify which files and context a reviewer needs
• Architecture Questions specify what system context enables useful advice
• Performance Issues list the metrics and profiles needed for diagnosis
• Integration Help identify which API docs and configs enable accurate guidance

Related Topics

When determining context needs, these prompts activate the skill:

• "What context do you need to help with this"
• "What information should I share for this task"
• "What files do you need to see"
• "Help me ask a better coding question"

Important Notes

Requirements

• A description of the coding task or problem to analyze
• Works with any programming language and framework
• Benefits from knowledge of the project structure for file recommendations
• No special tools or installations needed

Usage Recommendations

Do:

• Run this before asking complex questions to save back and forth time
• Share essential context items first and add helpful ones if needed
• Use priority rankings to decide what to include when time is limited
• Create templates for recurring tasks based on generated requirements

Don't:

• Skip essential context items as they are marked essential for a reason
• Dump entire codebases when the skill identifies specific files needed
• Ignore environment details since version mismatches cause many issues
• Assume the AI knows your project without providing the identified context

Limitations

• Context requirements are best guesses based on common patterns for each task type
• Unusual or novel problems may need context not covered by standard analysis
• Cannot assess the quality of context provided, only identify what is needed
• File recommendations assume standard project structures and may miss custom layouts