METAINFORMANT rules for directory tests/cstmm_fixture. 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.
Scanned 9/8/2026
Install to Claude Code
Skills Directorynpx -y skills add docxology/MetaInformAnt --skill metainformant-tests-cstmm-fixture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Metainformant Tests Cstmm Fixture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/docxology-metainformant-tests-cstmm-fixture)More formats (shields.io, HTML) on the badges page.
---
name: metainformant-tests-cstmm-fixture
description: METAINFORMANT rules for directory tests/cstmm_fixture. 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 — `tests/cstmm_fixture`
Before editing files in this subtree:
- Read [`AGENTS.md`](../../../tests/cstmm_fixture/AGENTS.md) for this folder (canonical technical context).
- Optional overview: [`README.md`](../../../tests/cstmm_fixture/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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
This skill helps you track, analyze, and report on keyword ranking positions over time. It monitors both traditional SERP rankings and AI/GEO visibility to provide comprehensive search performance insights.
