hitkeep-development

Name: hitkeep-development
Author: PascaleBeier

72stars6forks

How to install hitkeep-development?

pascalebeier/hitkeep/hitkeep-development

$npx -y skills add PascaleBeier/hitkeep --skill hitkeep-development

Installs into the current project.

Summary

Implement and route HitKeep contributions through the repository-owned hk developer platform. Use for any HitKeep code, UI, API, database, analytics-feature, seed, screenshot, documentation, integration, or release-preparation change, as well as setup, local development, builds,

Files · 1

View on GitHub

SKILL.md

1	# HitKeep Development
2
3	Treat `AGENTS.md` as policy and `hk` as workflow truth. Never copy commands, build tags, environment defaults, variants, ports, tool versions, or QA gates into another instruction surface.
4
5	## Connect
6
7	Use the central local HitKeep developer MCP for every operation it exposes. It is a root-routed stdio adapter over the same worktree-confined services as the CLI and is separate from the production analytics `/mcp` endpoint. A configured or enabled host entry is not enough; confirm that the relevant callable `hk_*` tools are exposed and make a read-only call before relying on MCP.
8
9	Follow this connection order:
10
11	1. Inspect the host's callable tools and select the relevant `hk_*` operation instead of translating it into shell.
12	2. Start with a read-only status or planning call and verify that its workspace ID matches the client's active root. If the client exposes multiple HitKeep roots, pass the intended root name, workspace ID, or path through the optional `workspace` input.
13	3. If tools are absent or fail, inspect host MCP health and compare the configured server name, executable, and arguments with `./hk mcp manifest --output json`. Report whether registration, startup, root routing, or task reload is blocking MCP. Existing tasks may need a host reload before a corrected registration becomes callable.
14	4. Obtain explicit user approval before invoking any equivalent structured CLI action. After approval, discover the command and flags through `./hk catalog commands --output json`, request `--output json`, and consume `schema_version`, `status`, `workspace_id`, `data`, and `error`. Stop on an unknown schema version instead of guessing.
15
16	Reserve direct `./hk` use for MCP bootstrap or repair, an explicitly approved fallback, and operations intentionally absent from MCP such as formatter or Go migration rewrites. Never guess a workspace or silently edit client-owned global configuration.
17
18	Use the typed MCP surface rather than translating an action into shell yourself:
19
20	- Diagnose with `hk_doctor`; start setup with `hk_setup_start` only when needed.
21	- Start, inspect, observe, or stop the workspace development session with `hk_dev_start`, `hk_dev_status`, `hk_dev_logs`, and `hk_dev_stop`.
22	- Capture local visual-QA routes with `hk_screenshot`; batch related routes so they share one browser session, and use returned resource links rather than copying images into the repository.
23	- Start deterministic builds and image smokes with `hk_build_start` and `hk_smoke_start`.
24	- Observe or cancel finite returned runs with `hk_run_status`, `hk_logs_tail`, and `hk_run_cancel`.
25
26	Development start and stop stream progress and component logging until they reach a stable result. Development log following ends on client cancellation without stopping the session. Finite MCP actions return run handles immediately; equivalent CLI actions use `--detach --output json`.
27
28	## Route the Work
29
30	- Use `$hitkeep-workspace` for worktree isolation, ports, services, long-running operations, concurrent agents, logs, or handoff.
31	- Use `$hitkeep-qa` for gate selection, execution, investigation, and completion evidence.
32	- Use `$hitkeep-i18n` when user-visible dashboard language or localized formatting changes.
33	- Load only the relevant reference below for implementation guidance. Do not create or load area-specific HitKeep skills alongside this one.
34
35	## Implementation References
36
37	- Read [backend.md](references/backend.md) for Go runtime, API, auth, MCP, AI, or DuckDB changes.
38	- Read [frontend.md](references/frontend.md) for Angular, dashboard UX, seed data, browser verification, or screenshots.
39	- Read [product.md](references/product.md) for product shaping or an end-to-end analytics feature.
40	- Read [delivery.md](references/delivery.md) for docs, OpenAPI, integrations, release preparation, or infrastructure-adjacent work.
41
42	## Workflow
43
44	1. Read `AGENTS.md`; inspect workspace status, the development session, and active finite runs before doing setup or starting services.
45	2. Diagnose prerequisites. Development is container-only. Run setup only when diagnostics or missing container dependencies require it; warm worktrees should reuse images and caches.
46	3. Read the variant resource/catalog once per task before development, build, or smoke work. Refresh it after pulling or rebuilding `hk`.
47	4. Start development only when the task needs services. Use the catalog-provided variant and returned URLs; never infer tags, defaults, or ports.
48	5. Treat development as a workspace session with cursor-addressed events. Treat screenshot capture as a bounded synchronous operation agai

People who liked this also viewed

6 picks

Type

hitkeep-development

72stars6forks

View on GitHub

How to install hitkeep-development?

pascalebeier/hitkeep/hitkeep-development

$npx -y skills add PascaleBeier/hitkeep --skill hitkeep-development

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# HitKeep Development
2
3	Treat `AGENTS.md` as policy and `hk` as workflow truth. Never copy commands, build tags, environment defaults, variants, ports, tool versions, or QA gates into another instruction surface.
4
5	## Connect
6
7	Use the central local HitKeep developer MCP for every operation it exposes. It is a root-routed stdio adapter over the same worktree-confined services as the CLI and is separate from the production analytics `/mcp` endpoint. A configured or enabled host entry is not enough; confirm that the relevant callable `hk_*` tools are exposed and make a read-only call before relying on MCP.
8
9	Follow this connection order:
10
11	1. Inspect the host's callable tools and select the relevant `hk_*` operation instead of translating it into shell.
12	2. Start with a read-only status or planning call and verify that its workspace ID matches the client's active root. If the client exposes multiple HitKeep roots, pass the intended root name, workspace ID, or path through the optional `workspace` input.
13	3. If tools are absent or fail, inspect host MCP health and compare the configured server name, executable, and arguments with `./hk mcp manifest --output json`. Report whether registration, startup, root routing, or task reload is blocking MCP. Existing tasks may need a host reload before a corrected registration becomes callable.
14	4. Obtain explicit user approval before invoking any equivalent structured CLI action. After approval, discover the command and flags through `./hk catalog commands --output json`, request `--output json`, and consume `schema_version`, `status`, `workspace_id`, `data`, and `error`. Stop on an unknown schema version instead of guessing.
15
16	Reserve direct `./hk` use for MCP bootstrap or repair, an explicitly approved fallback, and operations intentionally absent from MCP such as formatter or Go migration rewrites. Never guess a workspace or silently edit client-owned global configuration.
17
18	Use the typed MCP surface rather than translating an action into shell yourself:
19
20	- Diagnose with `hk_doctor`; start setup with `hk_setup_start` only when needed.
21	- Start, inspect, observe, or stop the workspace development session with `hk_dev_start`, `hk_dev_status`, `hk_dev_logs`, and `hk_dev_stop`.
22	- Capture local visual-QA routes with `hk_screenshot`; batch related routes so they share one browser session, and use returned resource links rather than copying images into the repository.
23	- Start deterministic builds and image smokes with `hk_build_start` and `hk_smoke_start`.
24	- Observe or cancel finite returned runs with `hk_run_status`, `hk_logs_tail`, and `hk_run_cancel`.
25
26	Development start and stop stream progress and component logging until they reach a stable result. Development log following ends on client cancellation without stopping the session. Finite MCP actions return run handles immediately; equivalent CLI actions use `--detach --output json`.
27
28	## Route the Work
29
30	- Use `$hitkeep-workspace` for worktree isolation, ports, services, long-running operations, concurrent agents, logs, or handoff.
31	- Use `$hitkeep-qa` for gate selection, execution, investigation, and completion evidence.
32	- Use `$hitkeep-i18n` when user-visible dashboard language or localized formatting changes.
33	- Load only the relevant reference below for implementation guidance. Do not create or load area-specific HitKeep skills alongside this one.
34
35	## Implementation References
36
37	- Read [backend.md](references/backend.md) for Go runtime, API, auth, MCP, AI, or DuckDB changes.
38	- Read [frontend.md](references/frontend.md) for Angular, dashboard UX, seed data, browser verification, or screenshots.
39	- Read [product.md](references/product.md) for product shaping or an end-to-end analytics feature.
40	- Read [delivery.md](references/delivery.md) for docs, OpenAPI, integrations, release preparation, or infrastructure-adjacent work.
41
42	## Workflow
43
44	1. Read `AGENTS.md`; inspect workspace status, the development session, and active finite runs before doing setup or starting services.
45	2. Diagnose prerequisites. Development is container-only. Run setup only when diagnostics or missing container dependencies require it; warm worktrees should reuse images and caches.
46	3. Read the variant resource/catalog once per task before development, build, or smoke work. Refresh it after pulling or rebuilding `hk`.
47	4. Start development only when the task needs services. Use the catalog-provided variant and returned URLs; never infer tags, defaults, or ports.
48	5. Treat development as a workspace session with cursor-addressed events. Treat screenshot capture as a bounded synchronous operation agai

People who liked this also viewed

6 picks

Type