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 a la instalación

Repositorio: stbenjam/daymark-public
Última actividad en el origen: 31 de julio de 2026 a las 18:41
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

3 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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.