AGENTS.md · git:20260713.114ecea · 2026-07-13 · sha256 ae94d1b695f21af2
AGENTS.md git:20260713.114eceaA
Immutable. This exact content is served forever at /api/v1/blob/ae94d1b695f21af2.
# Project conventions - instagram-skills
This file is for any Codex agent working on this repository. Read it before
making changes. Conventions here are mandatory unless the user asks otherwise.
## Versioning
- Single source of truth: `.codex-plugin/plugin.json`,
`.agents/plugins/marketplace.json`, `.claude-plugin/plugin.json`, and
`.claude-plugin/marketplace.json`. Plugin manifests must always match on
package name and version; marketplace entries must point to the same package;
author, license, homepage, and the public skill-bundle description must stay
aligned.
- Keep `AGENTS.md` and `CLAUDE.md` aligned when changing shared project rules.
Codex-specific workflow details belong here; Claude-specific details belong in
`CLAUDE.md`.
- Codex marketplace install uses `.codex-marketplace/instagram-skills/`. Do not
edit that generated package by hand. Update the root files first, then run
`python3 scripts/sync_codex_marketplace.py`.
- **Default: bump the PATCH segment (3rd level, `0.0.X`).** This is the automatic
behavior for every shippable commit, regardless of how large the diff feels.
Skill renames, lib API breaks, new features: still PATCH by default.
- Only bump MINOR or MAJOR when **the user explicitly asks** for a higher rank
("this is minor", "make it 2.0", "bump major"). Do not promote on your own
initiative even if semver textbook says so.
- After bumping, two steps are required:
1. Tag the commit: `git tag -a v<X.Y.Z> -m "..."` + `git push origin v<X.Y.Z>`
2. **Publish a GitHub Release** for the tag: `gh release create v<X.Y.Z> --title "v<X.Y.Z>" --notes "<changelog>" --latest`
A tag alone does NOT update the README release badge. The shields.io badge
reads from the Releases API, not from raw tags. Skipping step 2 leaves it stale.
## Commits
- Primary author **must** be Sergey: every `git commit` needs
`--author="Sergey Bulaev <s@bulaev.org>"`. Verify with
`git log -1 --format='%an <%ae>'` before pushing.
- Co-author trailers are fine when appropriate.
- Verify locally before push: build never breaks, no broken refs in `SKILL.md`,
library smoke import passes.
## Skill bundle invariants
- **Exactly 7 skills.** Adding requires merging or splitting elsewhere to stay at
7. The number is announced in plugin manifests and the README.
- **Frontmatter `description:` target <= 400 chars** (some bundle-heavy skills
land slightly higher when their scope is genuinely broad; keep under 510).
Always include a "Not for X (use Y)" disambiguation sentinel when a skill
overlaps with a sibling.
- **No em dashes anywhere in `description:` fields.** Em dashes in body prose are
allowed for table separators and list dividers only. No em dashes inside the
literal fill-in lines of any hook skeleton.
- **Skill names are public surface.** Renaming a skill is a major version bump and
requires updating: plugin manifests, marketplace entries, root `SKILL.md`
bundle list, README skill table, and every `ig-<name>` cross-reference in
sibling SKILL.md files.
## Voice rules + reference layout
- Canonical voice rules live at root `references/voice-rules.md`. Skill-local
"Hard rules" sections must only contain skill-specific overrides and start
with: `Global voice rules: see root SKILL.md Voice rules.`
- Other root-level references: `references/hook-formulas.md` (10 Instagram
formulas), `references/algorithm-heuristics.md`, `references/hashtag-strategy.md`,
and `references/media-workflow.md`.
- Skill-local references live in `skills/<skill>/references/`. Cite from the skill
with bare `references/X.md`. Cite root from skills with `../../references/X.md`.
- `ig-humanizer` has `sub-skills/` for the folded-in post-audit workflow.
## Layer separation
- **Write layer (Publora):** `lib/publora_client.py`. Instagram requires media on
every post, so the key method is `publish_media_post` (create draft, upload each
image/video, then schedule). Lower-level: `create_post`, `get_upload_url`,
`put_to_s3`, `update_post`, `delete_post`, and `list_connections` /
`instagram_connections` (GET /platform-connections). Skills call
`lib.publish(kind, draft_text, target_url, media=[...], ...)`. Real endpoints:
`POST /create-post`, `POST /get-upload-url`, `PUT /update-post/:id`,
`DELETE /delete-post/:id`, with `platforms: ["instagram-<id>"]` (array of
STRING ids), header `x-publora-key`.
- **Media is mandatory.** Text-only Instagram posts fail at publish time. The
writer skills produce the caption; the user supplies the media. `publish()`
only auto-posts on the Publora tier when `media` file paths are provided;
otherwise it returns the copy-paste caption block with a media reminder.
- **No read layer ships by default.** `ig-hook-extractor` asks the user to paste
the caption (and slide or Reel hook). Any future Instagram-read actor stays
gated behind `APIFY_TOKEN` with a paste fallback.
- Don't name competing third-party schedulers in committed files.
## Codex marketplace package
- Codex requires marketplace entries to point at a nested plugin directory. The
root remains the Claude-facing source layout.
- `.agents/plugins/marketplace.json` points to `.codex-marketplace/instagram-skills`.
- `scripts/sync_codex_marketplace.py` copies the root Codex manifest, `SKILL.md`,
`skills/`, `references/`, `lib/`, `scripts/`, `requirements.txt`, `.env.example`,
and `LICENSE` into the hidden package.
- After editing any copied file, run the sync script before testing or committing.
## testing/ is gitignored
- `testing/` is the local scratch directory: API keys, sample responses,
validation reports. Never write secrets above `testing/` (the rest of the repo
is public). The `.gitignore` rule for `testing/` is load-bearing.
## Validation before push
Run from repo root:
```bash
python3 -c "from lib import publish, parse_instagram_url, PubloraClient; print('OK')"
python3 scripts/sync_codex_marketplace.py
ls skills/ | wc -l # must equal 7
python3 -m json.tool .codex-plugin/plugin.json >/dev/null
python3 -m json.tool .agents/plugins/marketplace.json >/dev/null
python3 -m json.tool .claude-plugin/plugin.json >/dev/null
python3 -m json.tool .claude-plugin/marketplace.json >/dev/null
```
If any of these fail, do not push.