← all entries
A-TIER technique

GPT-6 Astra + Codex one-person company — context files and daily checkpoints

raycfu · 2026-09-09T03:37:27.000Z · in Creative
Open post ↗

100k ft — What is this?

GPT-6 Astra + Codex one-person company — context files and daily checkpoints
techniqueA-tier

50k ft — Why care?

Set up a workspace with three markdown context files (aboutme.md built from a 20-question interview, an anti-AI writing-style ban list, and mycompany.md with model, revenue and quarterly goals), then run Codex on GPT-6 Astra at three daily checkpoints: 8am inbox triage and call prep, noon delegation to sub-agents, 5pm audit whose summary seeds tomorrow's context.
agentsproductivityprompt engineeringvideo production

10k ft — Key takeaways

• A banned-phrases style file is the cheapest fix for AI-sounding output. • End-of-day audit summaries become next-day context: a continuous memory loop. • Give the model persistent identity/style/business context files instead of long prompts.

5k ft — Tools & techniques

Codex, OpenAI AI agents, context engineering, multi-agent delegation, scheduled agents

1k ft — Deep-dive / try it

How to run a one person company with GPT6 Astra and Codex #ai #tech
Transcript excerpt
Most people don't realize that you can use OpenAI, Aster, and Codex to set up a one-person company. Here's how you build it out. Most people get generic outputs because models have zero context on who you are, so you create a workspace with three different MD files. Start with the aboutme.md file by letting Aster interview about 20 questions on what you do, who you work with, what great deliverables look like, and what mistakes you hate. Then make the anti-AI writing style.md file. This is a strict list of everything it is not allowed to do when writing. Ban buzzwords, phrasing, and hard limits so your writing output doesn't look like ASL. Then make the my company.md file, which outlines your business models, target revenue, and quarterly goals. With Aster's built-in multi-agent delegation, you never have to write long prompts again. You just have to use this prompt structure above and into my guide at the end. Now you set up three automated checkpoints that run your entire day. At 8 a.m. when you wake up, Codex Aster has already sorted your inbox and written prep notes for every call. At noon, you brief it on afternoon deliverables, so it coordinates sub-agents in the background while you focus on client calls. At 5 p.m. and audits everything that was completed, what is pending, and what carries till tomorrow. The end-of-the-day summary automatically becomes your context for tomorrow, turning your entire operation into a continuous loop. I put together an exact sub-agent…

Appears in

More from @raycfu

Collection: Creative