How do I install the Init Context skill?

Run npx skillmds@latest add diegosouzapw/init-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Init Context safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Init Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Init Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Init Context?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Init Context by diegosouzapw — Agent Skill

Name: Init Context
Rating: 4.2 (5 reviews)
Author: diegosouzapw

File contents

Cursor Code Discovery - Automated Workflow

You are tasked with analyzing this codebase and completing Cursor rules files.

Inputs

Target directory (optional) - A particular directory within the codebase to focus on. If not provided, analyze the entire codebase.

Steps

Analyze the Codebase (or Directory) - Examine the codebase and gather information.
Populate Instruction Files - Use the existing files in .cursor/rules/.
Update Glob Patterns - If a target directory is provided, adjust the alwaysApply: true glob patterns accordingly.
Review Created Files - Confirm everything is accurate (make sure everything mentioned actually exists in the codebase).
Validate Formatting - Ensure proper formatting is followed based on the Guidelines below.

Key Analysis Areas

Overview: Business domain, key concepts, primary user types, integration points, key business workflows
Architecture & Patterns: Folder structure, module boundaries, layer dependencies, communication patterns, external service integrations
Stack Best Practices: Language-specific idioms, framework patterns, dependency injection patterns, error handling and validation patterns
Anti-Patterns: Logging of sensitive data, hardcoded secrets, non-parameterized SQL queries
Data Models: Core domain entities and relationships, key value objects and DTOs, data validation rules, database migration patterns
Security & Configuration: Environment variable management, secrets handling (1Password, vaults, etc.), authentication/authorization flow, API security patterns, compliance requirements
Commands & Scripts: Build scripts, deployment scripts, database migration commands, custom CLI tools

Guidelines

Each file MUST be 40 lines or fewer (including frontmatter)
Use bullet points and concise language
Preserve critical technical details
Include specific examples from THIS codebase
Adjust glob patterns as needed if a target directory is provided
Content should be specific to this repository, not generic advice

---name: init-contextdescription: Analyze the codebase and generate context rules for Cursor. Use when setting up or populating .cursor/rules/ files.---# Cursor Code Discovery - Automated WorkflowYou are tasked with analyzing this codebase and completing Cursor rules files.## Inputs1. Target directory (optional) - A particular directory within the codebase to focus on. If not provided, analyze the entire codebase.## Steps1. Analyze the Codebase (or Directory) - Examine the codebase and gather information.2. Populate Instruction Files - Use the existing files in `.cursor/rules/`.3. Update Glob Patterns - If a target directory is provided, adjust the `alwaysApply: true` glob patterns accordingly.4. Review Created Files - Confirm everything is accurate (make sure everything mentioned actually exists in the codebase).5. Validate Formatting - Ensure proper formatting is followed based on the Guidelines below.## Key Analysis Areas1. **Overview**: Business domain, key concepts, primary user types, integration points, key business workflows2. **Architecture & Patterns**: Folder structure, module boundaries, layer dependencies, communication patterns, external service integrations3. **Stack Best Practices**: Language-specific idioms, framework patterns, dependency injection patterns, error handling and validation patterns4. **Anti-Patterns**: Logging of sensitive data, hardcoded secrets, non-parameterized SQL queries5. **Data Models**: Core domain entities and relationships, key value objects and DTOs, data validation rules, database migration patterns6. **Security & Configuration**: Environment variable management, secrets handling (1Password, vaults, etc.), authentication/authorization flow, API security patterns, compliance requirements7. **Commands & Scripts**: Build scripts, deployment scripts, database migration commands, custom CLI tools## Guidelines- Each file MUST be **40 lines or fewer** (including frontmatter)- Use bullet points and concise language- Preserve critical technical details- Include specific examples from THIS codebase- Adjust glob patterns as needed if a target directory is provided- Content should be specific to this repository, not generic advice

Frequently asked questions

Init Context