learn
Provides autonomous project pattern learning by analyzing the codebase to discover development conventions, architectural patterns, and coding standards, then generates project rule files in .claude/rules/. Use when user asks to "learn from project", "extract project rules", "analyze codebase conventions", "discover project patterns", or wants to auto-generate Claude Code rules for the current project.
npx skills add majiayu000/claude-skill-registry --skill learn-giuseppe-trisciuogli-developer-kit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Learn Autonomously analyzes a project's codebase to discover development patterns, conventions, and architectural decisions, then generates project rule files in `.claude/rules/` for Claude Code to follow. ## Overview This skill acts as the **Orchestrator** in a two-agent architecture. It coordinates the overall workflow: gathering project context, delegating deep analysis to the `learn-analyst` sub-agent, filtering and ranking results, presenting findings to the user, and persisting approved rules to `.claude/rules/`. The separation of concerns ensures the analyst operates with a focused forensic prompt while the orchestrator manages user interaction and file persistence. ## When to Use Use this skill when: - User asks to "learn from this project" or "understand project conventions" - User wants to auto-generate `.claude/rules/` files from the existing codebase - User asks to "extract project rules" or "discover patterns" - User wants Claude Code to learn the project's coding standards - After joining a new project and wanting to codify existing conventions - Before starting a large feature to ensure Claude follows project patterns **Trigger phrases:** "learn from project", "ext
- Overview
- When to Use
- Instructions
- Phase 1: Project Context Assessment
- Phase 2: Delegate to Analyst Sub-Agent
- Phase 3: Review and Filter Results
- Phase 4: Present to User
- Phase 5: Persist Approved Rules
- Best Practices
- Constraints and Warnings
- Critical Constraints
- Limitations
- Examples
- Example 1: Learning from a NestJS project
Check for existing rules ls -la .claude/rules/ 2>/dev/null || echo "No .claude/rules/ directory found" cat CLAUDE.md 2>/dev/null || echo "No CLAUDE.md found" cat AGENTS.md 2>/dev/null || echo "No AGENTS.md found" ls -la .cursorrules 2>/dev/null || echo "No .cursorrules found" Quick project overview find . -type f -name "*.ts" -o -name "*.js" -o -name "*.java" -o -name "*.py" -o -name "*.go" -o -name "*.php" | wc -l mkdir -p .claude/rules
What does the learn skill do?
Provides autonomous project pattern learning by analyzing the codebase to discover development conventions, architectural patterns, and coding standards, then generates project rule files in .claude/rules/. Use when user asks to "learn from project", "extract project rules", "analyze codebase conventions", "discover project patterns", or wants to auto-generate Claude Code rules for the current project.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill learn-giuseppe-trisciuogli-developer-kit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
