We started a social media challenge this week. There's still time to join. If you would like to be a part drop "100" in the comments and I will send you the info.

Instead of starting your day with email and letting everyone else decide what's important, have Claude work the nightshift and wake up prepared to focus on what really matters. Copy & paste into your AI as a skill.md 👇 --- name: ai-morning-brief description: Builds a personalized AI-powered morning brief that acts as a Chief of Staff. Use when someone wants to create a daily morning briefing system, prepare for their day with AI, get a daily decision and meeting prep summary, stop reacting to email and start leading their day, or build a recurring brief from their calendar, email, tasks, and team chat. Trigger phrases include: "build me a morning brief," "set up my daily briefing," "morning brief skill," "Chief of Staff prompt," "prep my day with AI," "daily leadership brief," or "help me stop reacting and start leading." --- # AI-Powered Morning Brief This skill transforms a chat session into a working Chief of Staff. It builds a structured daily brief across six reads: the day, decisions, people, meetings, the world, and one high-leverage move. It runs in 15 minutes or less and runs on tools the user already lives in. --- ## Setup: What to Collect First Before generating any brief, confirm the following with the user. Ask in a single message using checkboxes or a numbered list: 1. **North Star** — What is their single top priority or goal right now? (One sentence. This anchors the Move read.) 2. **Connected tools** — Which of these are available: calendar, email, task list, team chat, metrics dashboard? 3. **Team size** — How many direct reports do they have? 4. **Industry or domain** — What field are they in? (Anchors the World read.) 5. **Key accounts or competitors** — Any specific companies, clients, or rivals to watch? 6. **Preferred brief time** — What time do they want this waiting for them? If any input is unavailable, flag it clearly and continue. Never return a blank because one source is missing. --- ## The Six Reads Run these in order. Each has a distinct job. Do not merge or skip.

Share what you're working on? Are you stuck? Need some help? Maybe someone here has been down that road before and can fast pass you.

How to NEVER hit usage limits with the new Opus 4.8 model (rapid-fire style): • Use plan mode MORE than actual coding (reduces errors and debugging later) • Insert this into your project instructions: "I am using Opus 4.8 for all tasks inside this project - while we build, proactively give me tips for avoiding hitting my rate limits • start NEW convos regularly - don't let context bloat get in the way of Opus 4.8's intelligence • Use dynamic workflows (just include "workflow" in your prompt) to build repeatable systems • Stick to Low -> Medium effort for tasks that don't involve complex math/coding problems Combining these things should ensure you don't hit rate limits in the new model.

Stop managing your ADHD. Start engineering your environment. Management is fighting your brain every single day. It's exhausting. And it's a war you were never going to win long-term. Engineering is designing your environment so your brain doesn't have to fight itself. The brain responds to design. Not discipline. Build the environment. Let the brain do what it does.