METAINFORMANT rules for directory docs/tasks. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
Installs into .claude/skills of the current project.
Are you the author of Metainformant Docs Tasks?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/docxology-metainformant-docs-tasks)
---
name: metainformant-docs-tasks
description: METAINFORMANT rules for directory docs/tasks. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
---
# METAINFORMANT — `docs/tasks`
Before editing files in this subtree:
- Read [`AGENTS.md`](../../../docs/tasks/AGENTS.md) for this folder (canonical technical context).
- Optional overview: [`README.md`](../../../docs/tasks/README.md).
- Global rules: [`CLAUDE.md`](../../../CLAUDE.md) at repo root (uv, `output/`, `.tmp/`, real implementations).
- Testing policy: [`docs/REAL_IMPLEMENTATION_POLICY.md`](../../../docs/REAL_IMPLEMENTATION_POLICY.md).
- Use `metainformant.core.io` for file I/O and `metainformant.core.utils.logging` for logs.
Keep changes scoped; match existing patterns in this directory.
