scan-project

Estrelas10

Forks0

Atualizado6 de julho de 2026 às 15:05

Use this skill when the user asks to explore, inspect, understand, map, or analyze a Symfony/API Platform repository before making changes. Trigger on requests like "look at this repo", "understand this project", "map the architecture", or "where should this change go?".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

thlaure

thlaure/world-cities-api

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	scan-project
description	Use this skill when the user asks to explore, inspect, understand, map, or analyze a Symfony/API Platform repository before making changes. Trigger on requests like "look at this repo", "understand this project", "map the architecture", or "where should this change go?".

Scan Project

Use this skill to build an implementation-ready map of the repository before coding.

Read first:

.claude/rules/architecture.md
.claude/rules/testing.md

Read as needed:

README.md
composer.json
Makefile
.claude/patterns.md

Workflow:

Inspect the project shape: src/, config/, tests/, features/, migrations/.
Identify the active conventions: Symfony version, API Platform usage, Docker/FrankenPHP setup, quality gates, and testing stack.
Find the nearest local example for the area the user wants to change.
Summarize architecture, likely files to touch, and main risks.

Rules:

Prefer local repository patterns over Symfony defaults.
Do not invent new layers or folders during the exploration phase.
Surface any CLAUDE.md rule that constrains implementation decisions.

Mais deste repositório

mesmo repositório

bug-fix

thlaure/world-cities-api

Use this skill when the user reports broken behavior, errors, regressions, failing tests, or asks to fix a bug. Trigger on requests like "this is broken", "fix this bug", "the test fails", or "there is a regression".

2026-07-0610

improve-instructions

thlaure/world-cities-api

Use this skill when the user asks to improve agent instructions, update Claude guidance, review drift in CLAUDE.md or .claude files, or keep the repo guidance aligned with how the project actually evolves.

2026-07-0610

karpathy-guidelines

thlaure/world-cities-api

Use for bug fixes, refactors, reviews, or ambiguity-heavy implementation tasks to reinforce explicit assumptions, minimal diffs, simplicity, and direct verification.

2026-07-0610

new-feature

thlaure/world-cities-api

Use this skill when the user asks to add, create, implement, or build new functionality in a Symfony/API Platform project. Trigger on requests like "add an endpoint", "implement a feature", "create a command", or "build this behavior".

2026-07-0610

prepare-commit

thlaure/world-cities-api

Use this skill when the user asks to prepare a commit, write a commit message, stage files, create a branch, prepare PR notes, or mentions Conventional Commits. Trigger on requests like "prepare the commit", "write the commit message", "stage this and prepare a PR", or "help me commit these changes".

2026-07-0610

review-change

thlaure/world-cities-api

Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Symfony/API Platform change follows project conventions. Trigger on "review this", "check my changes", or "is this implementation correct?".

2026-07-0610

name	scan-project
description	Use this skill when the user asks to explore, inspect, understand, map, or analyze a Symfony/API Platform repository before making changes. Trigger on requests like "look at this repo", "understand this project", "map the architecture", or "where should this change go?".

Scan Project

Use this skill to build an implementation-ready map of the repository before coding.

Read first:

.claude/rules/architecture.md
.claude/rules/testing.md

Read as needed:

README.md
composer.json
Makefile
.claude/patterns.md

Workflow:

Inspect the project shape: src/, config/, tests/, features/, migrations/.
Identify the active conventions: Symfony version, API Platform usage, Docker/FrankenPHP setup, quality gates, and testing stack.
Find the nearest local example for the area the user wants to change.
Summarize architecture, likely files to touch, and main risks.

Rules:

Prefer local repository patterns over Symfony defaults.
Do not invent new layers or folders during the exploration phase.
Surface any CLAUDE.md rule that constrains implementation decisions.