mcp-usage

bernardohaha's avatarfrom bernardohaha

Descreve como usar MCPs relevantes (filesystem, git, runtime) para trabalhar com o projeto Daylyou.

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 26, 2025

When & Why to Use This Skill

This Claude skill provides a comprehensive operational framework for using Model Context Protocol (MCP) tools—specifically Filesystem, Git, and Runtime—to streamline development on the Daylyou project. It establishes a standardized workflow for file manipulation, version control, and script execution, ensuring code consistency and reducing manual overhead for developers.

Use Cases

  • Safe Code Modification: Using the Filesystem MCP to read large files and apply precise patches, ensuring changes are restricted to the project directory.
  • Automated Version Control: Implementing a disciplined Git workflow that includes automated branch creation and micro-commits with standardized messaging for better project tracking.
  • Integrated Runtime Execution: Running development servers, linters, and test suites directly through the Runtime MCP to catch errors early and receive actionable feedback.
  • Structured Task Orchestration: Following a step-by-step 'Task Breakdown' to 'Commit' pipeline that synchronizes environment setup with code changes and validation.
namemcp-usage
descriptionDescreve como usar MCPs relevantes (filesystem, git, runtime) para trabalhar com o projeto Daylyou.

Skill: MCP Usage para o Daylyou

Filesystem MCP

  • Usa o filesystem MCP para:
    • ler ficheiros longos,
    • escrever alterações usando patches,
    • criar novos ficheiros ou pastas.
  • Nunca alteres ficheiros fora da pasta do projeto Daylyou.

Git MCP

  • Antes de um conjunto de alterações:
    • verifica o estado (git status);
    • cria uma branch nova (ex: feature/habits-layout).
  • Depois de completar uma micro-tarefa:
    • faz commit com mensagem clara (ex: feat(habits): add basic habits page layout).
  • Evita commits gigantes com mudanças misturadas.

Runtime MCP

  • Usa o runtime MCP para:
    • correr npm run dev ou npm run lint;
    • executar scripts específicos (ex: seed de dados, testes).
  • Se um comando falhar, lê o erro com atenção e devolve-me um resumo claro + sugestão.

Ordem recomendada numa tarefa grande

  1. Task Breakdown → plano de passos.
  2. Git → nova branch.
  3. Filesystem → editar ficheiros (safe-editing).
  4. Runtime → correr testes/dev server.
  5. Git → commit.