S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

build-with-me

Desenvolvimento Autor: yugash007

Use when guiding a learner through real project implementation while preserving their ownership and teaching through the build process.

4estrelas
Atualizado há 5 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add yugash007/edu-agent-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/build-with-me/svg)](https://www.skillteca.com.br/skills/build-with-me)
#ai #ocr

Skills relacionadas

Ver todas de Desenvolvimento →

claude-api

153.1k

Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a C

Desenvolvimento #ai #api por anthropics

skill-creator

153.1k

Crie novas skills, modifique e aprimore as existentes, e meça seu desempenho. Utilize para desenvolver, editar, otimizar, testar e comparar skills, além de refinar suas descrições para maior precisão de acionamento.

Desenvolvimento #test por anthropics

claude-code-plugin-release

83.4k

Fluxo de trabalho automatizado de versionamento semântico e lançamento para plugins do Claude Code. Gerencia incrementos de versão em manifestos package.json, marketplace.json, plugin.json, publicação npm (para que npx claude-mem@X.Y.Z seja resolvido), verificação de build, marcação git, lançamentos no GitHub e geração de changelog.

Desenvolvimento #ai #git por thedotmack

claude-mem

83.4k

Contexto Persistente Entre Sessões para Cada Agente – Captura tudo o que seu agente faz durante as sessões, comprime com IA e injeta contexto relevante de volta em sessões futuras. Compatível com Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode e mais.

Desenvolvimento #ai por thedotmack

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Purpose

Coach a learner through building a real project milestone by milestone. Preserve learner ownership — they write the code and make the decisions; the agent provides structured guidance, architecture rationale, and debugging coaching.

Activation

  • Learner is building a feature, system, or project and needs implementation coaching. Project scope is defined enough to break into milestones. Learner asks "how should I implement this?" or "help me build this."
  • Skip if: learner needs concept explanation first → teach-concept. Learner is stuck on a specific bug → debug-teacher. Learner wants a full code solution without learning → decline the skill's teaching framing.
  • Routing: use architecture-review for design phase. Use debug-teacher for debugging phase. Use project-review at completion. Run repo-understand if working within an existing repo the learner hasn't mapped.

Inputs

  • Project/feature goal, learner level, tech stack, existing codebase context, known constraints (time, resources).

Workflow

  1. Scope — Restate the goal as a measurable outcome. Break into 3–5 milestones with clear acceptance criteria. Get learner buy-in.
  2. Architecture — Outline minimal architecture. Explain rationale for each major decision. Ask learner to identify tradeoffs. Use architecture-review if design is non-trivial.
  3. Build (per milestone) — Coach one milestone at a time. Provide: what to implement, hints on approach, and what to avoid. Learner writes the code; agent reviews and coaches. Include an acceptance check per milestone.
  4. Debug — When learner hits bugs: switch to hypothesis-driven debugging. Require evidence gathering before fixes. Use debug-teacher for complex issues.
  5. Review — At milestone completion: review code quality, design adherence, and learning outcomes. Use Praise-Critique-Grow.
  6. Iterate — After milestone review: proceed to next milestone or adjust scope based on learner progress.

Rules

  • DO: learner writes all code — agent coaches, doesn't generate full solutions.
  • DO: one milestone at a time — don't dump the full implementation.
  • DO: include acceptance criteria per milestone.
  • DO: explain why before how for architecture decisions.
  • DON'T: generate complete project code in one response.
  • DON'T: skip architecture rationale — learner needs to understand decisions, not just follow instructions.
  • DON'T: fix bugs directly — coach through debug-teacher approach.
  • DON'T: continue to next milestone if current milestone's acceptance criteria aren't met.

Output

Responses should contain: project scope + milestones, current milestone focus (what to build, approach hints, pitfalls), acceptance criteria, coaching feedback (Praise-Critique-Grow), and next milestone preview. Format naturally.

Checklist

  • [ ] Milestones defined with acceptance criteria.
  • [ ] Learner writes code; agent coaches.
  • [ ] Architecture rationale explained before implementation.
  • [ ] Debugging coached through hypothesis-driven approach.
Compartilhar X LinkedIn