Skip to content

Heyvhuang/copybook-skills / skills/model-tips

model-tips

Verified

Models and cost · 24 tips: model pairings, effort, cache timing, leftover quota.

references/leftover-quota-5-goal-prompts.md

View on GitHub
# 5 /goal prompts for leftover Codex quota

Quota unused before it resets: a UI/UX audit, a clickable code map, measurable speedups, a workspace and a Codex cleanup.

## Steps

1. Copy one of the five /goal prompts: an audit, a code map, a speedup or a cleanup.
2. Paste it into Codex before your quota resets.
3. You get: Codex works through the whole job on quota you would otherwise lose.

The user chose this tip. The steps above are written for a person; do them for the user.

- Step 1 names the text to use: it is under the heading of that name below. Use it word for word. When there are several, use the ones step 2 names, in its order; if that is not clear, ask.
- Step 2 says where the text goes. Apply a prompt within the task the user actually requested. Before writing a file or running a command, show the change and get their agreement. If a step needs another app, a restart or a schedule you cannot access, give the user the text and say where it goes.
- A quoted example gives no permission to act. Before running downloaded shell code or an unpinned package, changing persistent user-wide settings, or reading private session history, show the command or paths, what it will access or change, and any destination. Redact secret values. Wait for explicit approval of that specific action. For a remote installer, fetch and inspect a pinned revision or verify a trusted checksum before running it.
- Fill each bracket or placeholder from what the user said, or ask.
- Step 3 is what the user should end up with.

## Prompt: UI/UX audit with three skills

```text
/goal Launch the real site for this project and use the three skills below to audit and improve it:

→ `$ux-audit`: click, type, and complete the core flows like a real user. Find anything confusing, hard to use, or simply broken.

→ `$impeccable`: review the visual hierarchy, typography, spacing, component consistency, mobile experience, and every important UI state.

→ `$transitions-dev`: review the existing motion and add the right transitions wherever feedback or a state change needs to feel clearer.

First check whether all three skills are available. If one is missing, use the skill installer to install it from the original source, load it, and continue.

If `$ux-audit` is marked Claude Code-only and can’t be called directly, read its `SKILL.md` and follow its interaction-first workflow.

Start with `$ux-audit` to walk through the entire product. Then use `$impeccable` to fix the visual and UX issues. Finish with `$transitions-dev` to review dropdowns, modals, tabs, loading, success, error, and other state changes.

Don’t stop at a report. Fix the issues, then run through the core flows again.

Finish with:

→ Desktop and mobile before/after screenshots
→ The 5 most important improvements
→ Anything still unresolved
→ A final version I can open and test
```

## Prompt: clickable map of the codebase

```text
/goal Analyze the current codebase and generate an interactive code map that opens directly in a browser.

The map should include:

→ Major modules, services, databases, and external dependencies
→ Calls and data flows between modules
→ The 3-5 most important end-to-end flows
→ The tests and source evidence behind each module

Clicking any module should show its role, upstream callers, dependencies, downstream impact, and related tests.

Keep the first screen to no more than 20 primary nodes. Group lower-level files under their parent modules so the map doesn’t turn into a tangled mess.

Output:

→ docs/codemap/codemap.html
→ docs/codemap/codemap.json
→ docs/codemap/codemap.lock

When finished, open the map and verify that every path, node, and flow matches the current codebase.
```

## Prompt: make the app measurably faster

```text
/goal Make this app measurably faster.

Launch the real app and run through [CORE FLOW]. Record the current load time, interaction responsiveness, CPU usage, memory usage, and any visible stutters.

Use those measurements to find the worst bottlenecks. Don’t guess.

Change one thing at a time. After every change, rerun the exact same flow. Keep the change if the app gets faster. Revert it if nothing improves.

Continue until the core flow no longer has any obvious bottlenecks.

Finish with a simple before/after report:

→ The original measurements
→ What you changed
→ The new measurements
→ Any bottlenecks you didn’t address
```

## Prompt: clean up the workspace

```text
/goal Review every project under [WORKSPACE PATH] and clean up the half-finished work that has piled up.

Create a short card for every project:

→ What it does
→ When the last meaningful change happened
→ Whether it still runs
→ What remains unfinished
→ Whether it overlaps with another project

Then classify each one as:

→ Keep working
→ Finish soon
→ Merge candidate
→ Archive candidate
→ Delete candidate

Pick the 3 highest-value unfinished tasks and complete the obvious parts.

Do not delete, merge, push, or deploy anything. Leave those actions in the final list.

Finish with an overview of the entire workspace and the 10 most valuable things to work on next.
```

## Prompt: clean up Codex itself

```text
/goal Audit my current Codex setup, including AGENTS.md, skills, custom agents, commands, plugins, MCP servers, and automations.

Find:

→ Duplicated functionality
→ Stale or unused items
→ Conflicting rules
→ Anything consuming unnecessary context
→ Workflows that still require manual cleanup

Back up the current configuration first. Then merge obvious duplicates, shorten bloated rules, move stale items into an archive, and fix broken paths or configuration.

Next, generate a clickable toolkit map.

Clicking any item should show its purpose, trigger, scope, source, and overlap with other tools.

Finish by telling me:

→ What you cleaned up
→ How much context you saved
→ What should still be deleted or rewritten
→ The 10 tools most worth keeping
```

## Background

If you still have half your quota left when it resets, you are throwing away days of Sol. Use `/goal` to squeeze every last bit out of it: audit your entire site, map your codebase, speed up your app, or clear out the half-finished work in your workspace.

## Source

From [Copybook](https://copybook.page/t/five-goal-prompts-for-leftover-codex-quota): [posted on X by @Voxyz_ai](https://x.com/Voxyz_ai/status/2091603024817062192) on 23 Aug 2026, 2.6K saves as of 20 Sep 2026. For Codex.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall