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.

Jump to install

Repository: stbenjam/daymark-public
Last source activity: July 31, 2026 at 18:41
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

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

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

3 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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.