Source of truth for the public HagiTask community task definitions.
The user-facing contribution walkthrough is maintained in the HagiTask community guide. This README is intentionally limited to repository boundaries, source layout, schema references, and validation commands.
Contributors edit data/<taskId>/ in this repository. HagiTask Site consumes a pinned commit,
validates the source packages, and generates the public catalog and archives:
| Artifact | Owner |
|---|---|
data/<taskId>/ |
This repository; editable package source |
node_modules/@hagicode/hagitask/ |
Pinned CLI and shared schema source |
/index.json |
Generated by HagiTask Site |
/tasks/<taskId>.json |
Generated by HagiTask Site |
/packages/<taskId>.zip |
Generated by HagiTask Site |
Do not commit generated catalog JSON, package archives, or build output here. The ZIP contains
the complete data/<taskId>/ directory, so package resources are published from source.
data/<taskId>/
manifest.json
frontend/
panel.json
commands.json # optional
backend/
task-preset.json
prompts.json
templates/<locale>/
system.md
user.hbs
locales/
en-US.json
zh-CN.json
store-page/
index.en-US.md
index.zh-CN.md
The directory name is the canonical taskId and must match manifest.json's
taskPresetId. The full ID rules, required resources, locale/store-page behavior, versioning,
and Pull Request process are documented in the
community guide.
The published @hagicode/hagitask CLI is the
authoritative schema source. Package $schema values use the public distribution root:
https://tasks.hagicode.com/schemas/task-preset-plugin/<schema>.schema.json
| Package file | Schema URL suffix |
|---|---|
manifest.json |
manifest.schema.json |
frontend/panel.json |
panel.schema.json |
frontend/commands.json |
commands.schema.json |
backend/task-preset.json |
task-preset.schema.json |
backend/prompts.json |
prompt-package.schema.json |
locales/<locale>.json |
locales.schema.json |
Generated catalog schemas are published by HagiTask Site and are not authored here.
npm ci
npm run validateRun the validator tests when changing validation tooling:
npm testFix validation errors in data/<taskId>/. Do not remove $schema references, relax the
contract locally, or patch generated output.
Enabled task target selections may use owner-project-repositories, vault-registry, or
project-registry. Unknown scope sources fail validation with a selection-specific diagnostic
before publication.
- This repository is the only source of truth for community task definitions.
- Do not duplicate package definitions inside HagiTask Site.
- Do not copy or edit local schema files; schema changes belong in HagiTask and its published CLI.
- Bump
manifest.json's semantic version for every published package change. - Submit package Pull Requests to this repository, not HagiTask Site or HagiTask.
For the complete creation, validation, publishing, and troubleshooting flow, follow the HagiTask community guide.