mathodology-project-orientation

Name: mathodology-project-orientation
Author: sweetcornna

36stars5forks

How to install mathodology-project-orientation?

sweetcornna/mathodology/mathodology-project-orientation

$npx -y skills add sweetcornna/mathodology --skill mathodology-project-orientation

Installs into the current project.

Summary

Use when maintaining, validating, or checking boundaries of the Mathodology skills repository itself, or deciding whether a change belongs on this branch.

Files · 1

View on GitHub

SKILL.md

1	# Mathodology Project Orientation
2
3	## Repository Contract
4
5	This branch is a skills-only GitHub tree. Treat it as an AI-coding knowledge pack, not as the original runnable Mathodology application.
6
7	Current work should normally edit only:
8
9	- any file under `.claude/skills/<skill-name>/` — its `SKILL.md`,
10	`agents/openai.yaml`, and a `scripts/` directory when the skill ships one
11	(e.g. `.claude/skills/mathodology-award-gates/**` and
12	`.claude/skills/mathodology-dev-test-release/scripts/validate_repo.py`)
13	- `.claude/agents/<agent-name>.md` (including `.claude/agents/mathodology-award-judge.md`)
14	- `.claude/workflows/<workflow-name>.md`
15	- `.claude/skills/mathodology-whole-project/scripts/create-source-backup.sh`
16	- `AGENTS.md`
17	- `README.md`
18	- `README_en.md`
19	- `docs/SKILLS.md`
20	- `docs/SKILLS_zh.md`
21	- `docs/INSTALL.md`
22	- `docs/INSTALL_zh.md`
23	- `docs/WORKFLOWS.md`
24	- `docs/WORKFLOWS_zh.md`
25	- `docs/BACKUP.md`
26	- `.gitignore`
27
28	`LICENSE` is retained but should not change unless the license changes.
29
30	## What Is Absent
31
32	The current GitHub tree should not contain application source, generated clients, CI, deployment, package-manager, installer, data, or test trees.
33
34	If a task requires historical implementation detail, use Git history or another branch in a separate worktree. Do not add those files back to this branch as part of ordinary skills maintenance.
35
36	## Boundary Check
37
38	Before publishing cleanup or skill maintenance, verify tracked files stay inside
39	the skills-repository whitelist:
40
41	```bash
42	python3 .claude/skills/mathodology-dev-test-release/scripts/validate_repo.py whitelist
43	```
44
45	Run `validate_repo.py all` for the full set of maintenance gates (skills,
46	metadata, links, whitelist, agents, sync). The whitelist logic lives only in
47	that script; do not re-inline it here.
48
49	## Text Check
50
51	Search for stale current-path claims before committing (requires ripgrep; the
52	`grep -E` fallback is shown second):
53
54	```bash
55	rg -n "apps/\|crates/\|packages/\|docs/skills\|Dockerfile\|docker-compose\|just \|cargo\|pnpm\|uv run\|\.github\|installer" README.md README_en.md AGENTS.md docs .claude/skills
56	grep -REn "apps/\|crates/\|packages/\|docs/skills\|Dockerfile\|docker-compose\|just \|cargo\|pnpm\|uv run\|\.github\|installer" README.md README_en.md AGENTS.md docs .claude/skills
57	```
58
59	Hits are acceptable only when they describe removed historical material or an absence check. They must not instruct agents to edit or run missing current files. The current skills, scripts, and award-gate content do not match this pattern, so any hit is a stale claim to review.
60
61	## Choosing Skills
62
63	- Whole repository backup, transfer, or orchestration: use `mathodology-whole-project`.
64	- Skill text or metadata changes: use `mathodology-skill-authoring`.
65	- Award-level Codex or Claude Code phase workflow: use `docs/WORKFLOWS.md`.
66	- Award-run gate schemas (handoff/gate/scorecard/decision_memo), judge-panel protocol, and figure/PDF QA scripts: use `mathodology-award-gates`.
67	- Former subsystem knowledge: use the matching archived subsystem skill.
68	- Validation and publishing checks: use `mathodology-dev-test-release`.

People who liked this also viewed

6 picks

Type

mathodology-project-orientation

36stars5forks

View on GitHub

How to install mathodology-project-orientation?

sweetcornna/mathodology/mathodology-project-orientation

$npx -y skills add sweetcornna/mathodology --skill mathodology-project-orientation

Installs into the current project.

Summary

Use when maintaining, validating, or checking boundaries of the Mathodology skills repository itself, or deciding whether a change belongs on this branch.

Files · 1

View on GitHub

SKILL.md

1	# Mathodology Project Orientation
2
3	## Repository Contract
4
5	This branch is a skills-only GitHub tree. Treat it as an AI-coding knowledge pack, not as the original runnable Mathodology application.
6
7	Current work should normally edit only:
8
9	- any file under `.claude/skills/<skill-name>/` — its `SKILL.md`,
10	`agents/openai.yaml`, and a `scripts/` directory when the skill ships one
11	(e.g. `.claude/skills/mathodology-award-gates/**` and
12	`.claude/skills/mathodology-dev-test-release/scripts/validate_repo.py`)
13	- `.claude/agents/<agent-name>.md` (including `.claude/agents/mathodology-award-judge.md`)
14	- `.claude/workflows/<workflow-name>.md`
15	- `.claude/skills/mathodology-whole-project/scripts/create-source-backup.sh`
16	- `AGENTS.md`
17	- `README.md`
18	- `README_en.md`
19	- `docs/SKILLS.md`
20	- `docs/SKILLS_zh.md`
21	- `docs/INSTALL.md`
22	- `docs/INSTALL_zh.md`
23	- `docs/WORKFLOWS.md`
24	- `docs/WORKFLOWS_zh.md`
25	- `docs/BACKUP.md`
26	- `.gitignore`
27
28	`LICENSE` is retained but should not change unless the license changes.
29
30	## What Is Absent
31
32	The current GitHub tree should not contain application source, generated clients, CI, deployment, package-manager, installer, data, or test trees.
33
34	If a task requires historical implementation detail, use Git history or another branch in a separate worktree. Do not add those files back to this branch as part of ordinary skills maintenance.
35
36	## Boundary Check
37
38	Before publishing cleanup or skill maintenance, verify tracked files stay inside
39	the skills-repository whitelist:
40
41	```bash
42	python3 .claude/skills/mathodology-dev-test-release/scripts/validate_repo.py whitelist
43	```
44
45	Run `validate_repo.py all` for the full set of maintenance gates (skills,
46	metadata, links, whitelist, agents, sync). The whitelist logic lives only in
47	that script; do not re-inline it here.
48
49	## Text Check
50
51	Search for stale current-path claims before committing (requires ripgrep; the
52	`grep -E` fallback is shown second):
53
54	```bash
55	rg -n "apps/\|crates/\|packages/\|docs/skills\|Dockerfile\|docker-compose\|just \|cargo\|pnpm\|uv run\|\.github\|installer" README.md README_en.md AGENTS.md docs .claude/skills
56	grep -REn "apps/\|crates/\|packages/\|docs/skills\|Dockerfile\|docker-compose\|just \|cargo\|pnpm\|uv run\|\.github\|installer" README.md README_en.md AGENTS.md docs .claude/skills
57	```
58
59	Hits are acceptable only when they describe removed historical material or an absence check. They must not instruct agents to edit or run missing current files. The current skills, scripts, and award-gate content do not match this pattern, so any hit is a stale claim to review.
60
61	## Choosing Skills
62
63	- Whole repository backup, transfer, or orchestration: use `mathodology-whole-project`.
64	- Skill text or metadata changes: use `mathodology-skill-authoring`.
65	- Award-level Codex or Claude Code phase workflow: use `docs/WORKFLOWS.md`.
66	- Award-run gate schemas (handoff/gate/scorecard/decision_memo), judge-panel protocol, and figure/PDF QA scripts: use `mathodology-award-gates`.
67	- Former subsystem knowledge: use the matching archived subsystem skill.
68	- Validation and publishing checks: use `mathodology-dev-test-release`.

People who liked this also viewed

6 picks

Type