Support local Codex custom prompts and $skills in the composer

[paul-bouzian]

Problem

T3 Code is Codex-first, but the composer currently misses two local Codex CLI affordances that are part of the normal prompt-entry workflow:

• local custom prompts from ~/.codex/prompts/*.md
• local $skills invocation with autocomplete and exact skill binding

Today, typing / only shows built-in commands, and typing $ does not surface local Codex skills.

Expected behavior

Match Codex CLI behavior closely for local prompts and local skills:

• / should include local custom prompts as /prompts:<name>
• /code should be able to match /prompts:code-simplifier
• selecting a custom prompt should insert /prompts:<name> into the composer
• sending /prompts:<name> ... should expand the prompt locally before dispatch
• $ should open a local Codex skills menu
• selecting a skill should insert $<name> into the composer
• duplicate skill names should stay distinct in the menu using their path / scope
• selected skills should be sent to Codex as explicit structured skill items, not only raw text
• Enter / Tab should accept the highlighted menu item without sending the message

Why this should exist

These are not new product directions so much as Codex compatibility gaps in the primary Codex workflow.

Without them, T3 Code is missing a meaningful part of the day-to-day Codex CLI input model for users who rely on:

• reusable local prompts
• reusable local skills
• duplicate-skill disambiguation

Proposed delivery

To keep review scope small, I plan to split this into two focused PRs:

1. local custom prompt discovery, autocomplete, and send-time expansion
2. local $skills autocomplete and structured skill dispatch

Notes

• Scope is local Codex prompts and local Codex skills only
• No new provider work is involved
• I can add Codex CLI reference screenshots and before/after UI captures in follow-up comments if that is helpful for review

[notkainoa]

Also pulling skills from the global .agents/skills folder would be nice

[paul-bouzian]

Also pulling skills from the global .agents/skills folder would be nice

definitly adding this to the PRs

[jameswasher]

Adding a concrete repo-scoped repro for this.

I tested this with a custom Codex skill in a real project.

Paths tested:

• .codex/skills/<skill-name>/SKILL.md
• .agents/skills/<skill-name>/SKILL.md

Skill metadata:

• valid name: in frontmatter
• intended invocation via slash or $ skill syntax

What I observed in T3 Code:

• typing the matching prefix after / does not show the custom skill
• typing the matching prefix after $ does not show the custom skill
• fully quitting and reopening T3 Code does not change behavior
• the skill is not discoverable from either .codex/skills or .agents/skills

Control case:

• the same skill works in Codex
• this strongly suggests a T3 Code Codex-compatibility gap rather than a malformed SKILL.md

Expectation:

• if T3 is aiming for Codex-compatible local skills, repo-scoped skills should be discovered and surfaced in the composer
• at minimum, $<skill-name> should bind the local skill
• ideally, enabled skills should also appear in the slash menu if T3 intends to surface them there

Happy to provide a minimal sample SKILL.md if useful, but this repro should already be enough to validate discovery/composer behavior.

[juliusmarminge]

skills ui added.

will think on prompts

[respectTheCode]

Does this work with codex? I only see App and System skills. No User or Repo skills show up in the composer. Codex in T3 does find and use repo skills if asked though.