init-project
Skill0 starsChanged 6 months agoMITView on GitHub
Macro-skill que inicializa projeto novo em 3 sub-etapas sequenciais: /setup-architecture, /setup-design e /setup-infra. Exibe plano completo ao operador antes de executar. Recebe descricao do projeto como argumento.
49 other projects use a version of this.
Adopted by
Most recently taken up by
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- ryanportfolio/winuse-mcptheir own version, first seen Nov 8, 2026
- eugenelim/agent-ready-repotheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 7, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 7, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
- ryanportfolioSkill
apply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- southliu/south-admin-react★ 582same name
- wataru-maeda/react-native-boilerplate★ 521same name
- flonat/flonat-research★ 150same name
- huangwb8/skills★ 50same name
- jiahao-shao1/sjh-skills★ 43same name
- eugenelim/agent-ready-repo★ 28same name
- freemty/labmate★ 25same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- eranw2000/multi-phase-skills-framework★ 10same name
39 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- frontend/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- frontend/CLAUDE.mdCLAUDE.md
- add-entity-to-auditSkill
- auditSkill
- babysit-prsSkill
- batchSkill
- daily-summarySkill
- factory-metricsSkill
- feature-frontSkill
- featureSkill
- migrateSkill
- planSkill
- register-screenSkill
- review-archSkill
- review-frontSkill
- review-prSkill
- setup-architectureSkill
- setup-designSkill
- setup-infraSkill
- shipSkill
- tasksSkill
- watch-ciSkill
- write-jobSkill
- write-migrationSkill
- write-reportSkill
- write-testSkill
The file
Files
Voce deve inicializar um projeto novo em 3 sub-etapas sequenciais. Execute todos os passos em ordem. Nao use a Skill tool para invocar sub-etapas -- leia os arquivos SKILL.md e execute a logica manualmente.
Input
Argumento recebido: descricao do projeto com flags opcionais. Exemplos:
"sistema de gestao de tarefas""e-commerce de livros usados --figma https://figma.com/file/abc123"
Passo 0 -- Parsear argumentos
Extrair da string de argumento recebida:
- descricao: tudo antes de
--figma(se presente), com trim. Se nao houver--figma, a string inteira. - figmaUrl: valor apos
--figma(se presente), com trim. Null se ausente.
Validar:
descricaonao pode ser vazia nem apenas espacos.- Se vazia: exibir "ERRO: descricao do projeto e obrigatoria. Uso: /init-project
<descricao>[--figma<url>]" e terminar.
Passo 1 -- Exibir plano completo e aguardar aprovacao
Exibir ao operador:
/init-project: inicializando projeto "<descricao>"
Plano de execucao (3 sub-etapas sequenciais):
[1] /setup-architecture "<descricao>"
Define linguagem, framework e arquitetura do projeto.
Gera: docs/architecture.md
Aguarda aprovacao do operador antes de prosseguir.
[2] /setup-design "<descricao>"[--figma <url>]
Propoe paleta de cores, tipografia, componentes e mapeamentos de tipo-de-dado.
Gera: docs/design-system.md + componentes wrapper em frontend/src/shared/components/
Aguarda aprovacao do operador antes de prosseguir.
[3] /setup-infra "<descricao>"
Define CI/CD, Docker, banco de dados e hooks de qualidade.
Gera: .github/workflows/ci.yml, docker-compose.yml
Aguarda aprovacao do operador antes de prosseguir.
Cada sub-etapa exibe sua proposta e aguarda aprovacao individual.
O operador pode cancelar em qualquer ponto.Usar AskUserQuestion com a pergunta "Iniciar /setup-architecture agora?" Opcoes: "Sim, iniciar" e "Nao, cancelar".
Se cancelar: exibir "Execucao cancelada. Nenhum arquivo gerado." e terminar.
Passo 2 -- Executar /setup-architecture
Ler o arquivo .claude/skills/setup-architecture/SKILL.md.
Executar a logica descrita nele manualmente, passo a passo, passando descricao como argumento.
A propria sub-etapa fara AskUserQuestion para aprovacao interna. Se o operador cancelar dentro da sub-etapa: exibir "Sub-etapa 1 cancelada. /init-project encerrado." e terminar.
Ao concluir: confirmar que docs/architecture.md foi gerado:
Test-Path docs/architecture.mdSe nao existir e sub-etapa nao foi cancelada: reportar como erro critico e terminar.
Passo 3 -- Executar /setup-design
Ler o arquivo .claude/skills/setup-design/SKILL.md.
Executar a logica descrita nele manualmente, passando:
descricaocomo dominio do projetofigmaUrlcomo referencia visual (se presente)
A propria sub-etapa fara AskUserQuestion para aprovacao interna. Se o operador cancelar dentro da sub-etapa: exibir "Sub-etapa 2 cancelada. /init-project encerrado." e terminar.
Se o arquivo .claude/skills/setup-design/SKILL.md nao existir: reportar como aviso e pular esta
sub-etapa, continuando para o Passo 4. Registrar no relatorio final: "/setup-design: PULADO (arquivo nao encontrado)".
Passo 4 -- Executar /setup-infra
Ler o arquivo .claude/skills/setup-infra/SKILL.md.
Executar a logica descrita nele manualmente, passando descricao como argumento.
A propria sub-etapa fara AskUserQuestion para aprovacao interna. Se o operador cancelar dentro da sub-etapa: exibir "Sub-etapa 3 cancelada. /init-project parcialmente concluido (1 e 2 OK)." e terminar.
Ao concluir: confirmar que .github/workflows/ci.yml foi gerado:
Test-Path .github/workflows/ci.ymlPasso 5 -- Relatorio final
Exibir:
/init-project concluido.
Projeto: <descricao>
Sub-etapas executadas:
[1] /setup-architecture: OK -- docs/architecture.md gerado
[2] /setup-design: OK -- docs/design-system.md gerado
[3] /setup-infra: OK -- .github/workflows/ci.yml, docker-compose.yml gerados
Proximos passos:
1. Revisar cada arquivo gerado em docs/
2. Commitar: feat(init): inicializa projeto <descricao>
3. Invocar /ship para abrir PRAdaptar o status de cada sub-etapa conforme resultado real (OK, PULADO, CANCELADO).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.