Has anybody else used this? I bookmarked it. I never did go back and try it out, but it looks actually really cool. Built by ex-AI engineers from Meta, Microsoft, and Amazon. Launch & Control Claude Code from Anywhere Stop being chained to your desk. The real-time command center to monitor, debug, and guide your agent—right from your phone. https://omnara.com/

I really like this one. I know that this is part of the GPT-5 prompting guide GPT-5 prompting guide but I really don't think it matters what LLM you're using. Could go into Cursor Rules or Claude MD When implementing incremental changes and refactors in existing apps, model-written code should adhere to existing style and design standards, and “blend in” to the codebase as neatly as possible. Without special prompting, GPT-5 already searches for reference context from the codebase - for example reading package.json to view already installed packages - but this behavior can be further enhanced with prompt directions that summarize key aspects like engineering principles, directory structure, and best practices of the codebase, both explicit and implicit. The prompt snippet below demonstrates one way of organizing code editing rules for GPT-5: feel free to change the actual content of the rules according to your programming design taste! <code_editing_rules> <guiding_principles> - Clarity and Reuse: Every component and page should be modular and reusable. Avoid duplication by factoring repeated UI patterns into components. - Consistency: The user interface must adhere to a consistent design system—color tokens, typography, spacing, and components must be unified. - Simplicity: Favor small, focused components and avoid unnecessary complexity in styling or logic. - Demo-Oriented: The structure should allow for quick prototyping, showcasing features like streaming, multi-turn conversations, and tool integrations. - Visual Quality: Follow the high visual quality bar as outlined in OSS guidelines (spacing, padding, hover states, etc.) </guiding_principles> <frontend_stack_defaults> - Framework: Next.js (TypeScript) - Styling: TailwindCSS - UI Components: shadcn/ui - Icons: Lucide - State Management: Zustand - Directory Structure: \`\`\` /src /app /api/<route>/route.ts # API endpoints /(pages) # Page routes

Hey everyone! So diving deep into Cursor lately, and I ran into this little annoyance that maybe some of you have noticed too. You know how Cursor shows you that usage percentage at the bottom of the agent window? Well, I kept wanting to know if I was burning through my monthly allowance too fast or if I was actually pacing myself well. The thing is, it's not super obvious how far through your billing month you are without doing some mental math. Like, my subscription renews on the 19th of each month, so if it's the 26th today, how much of my billing period have I actually used up? I ended up creating a simple prompt that calculates exactly where you are in your current billing cycle as a percentage. Then you can just compare that number against your Cursor usage percentage - if your usage is higher than your billing cycle progress, you know you're going a bit heavy this month. If it's lower, you're golden. Here's the prompt if anyone wants to try it: "You will act as a subscription usage calculator and tracker. I have a subscription service that operates on a monthly cycle from the 19th of one month to the 19th of the next month (inclusive on both ends). When I provide you with a current date, perform the following calculations and provide this information: 1. First, confirm the current date being calculated: "Calculating for: [Date]" 2. Identify the current subscription period (show the exact date range) 3. Calculate the total number of days in this specific period (accounting for actual calendar days including leap years) 4. Calculate how many days have elapsed (including both the 19th and the current date) 5. Calculate the percentage of the period that has elapsed (rounded to two decimal places) 6. Show the number of days remaining in the current period 7. Display a visual progress bar with the percentage either directly above or below it, like this: 25.81% [████░░░░░░░░░░░░░░░░] For your calculations, always use the actual number of days in each month (28/29 for February, 30 for April/June/September/November, 31 for other months).

Go from design to code with GPT-5-Codex and Agent https://x.com/cursor_ai/status/1970597431315144855

Played around with Manus and really enjoyed the fast research paper and presentation outputs. Have you played around with Manus? What do you think?