daymark-development

Develop, refactor, diagnose, or review the Daymark Flask, SQLite, worker, MCP, monitor, report, project, meeting, agent-runner, and UI code. Use for changes in the Daymark repository that must preserve isolated production state and follow its package boundaries, migration rules, and verification workflow.

Ir para a instalação

Repositório: stbenjam/daymark-public
Última atividade na origem: 31 de julho de 2026 às 18:41
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

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ê.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/stbenjam/daymark-public --skill daymark-development

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

3 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

Daymark Development

Use this skill for repository work on Daymark. Read AGENTS.md first, then consult docs/architecture.md for package ownership. Load references/verification.md when the task changes code, packaging, migrations, or deployment. Keep the generated Codex interface metadata in agents/openai.yaml aligned with this workflow.

Work safely

Inspect git status before editing and preserve unrelated changes.

Work only in the development checkout. Never mutate or restart the production checkout unless the user explicitly authorizes deployment.

Keep runtime data, copied databases, credentials, logs, PID files, and generated agent workspaces outside Git.

Use a temporary DAYMARK_DATA_DIR for runtime and migration checks.

Place changes

Put HTTP and UI coordination in daymark.web.

Put durable operations and explicit forward migrations in daymark.storage.

Put harness-neutral model execution in daymark.ai; select harness and model through configuration.

Put MCP tools in the matching module under daymark.mcp.

Put domain behavior in projects, meetings, monitors, reports, or journal, keeping Flask and SQLite mechanics at their boundaries.

Add package assets under daymark/templates or daymark/static.

Prefer focused modules and public domain operations over route-local logic, cross-package private imports, or compatibility shims.

Verify and hand off

Run focused tests while iterating, then complete the checklist in references/verification.md. Report which checks passed and any unverified external behavior. When publication is requested, commit only intentional changes, push the feature branch, and open a draft pull request with the behavioral impact and verification results.