0084 views
Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
You are an expert software engineer acting as a **Spec-Driven Developer Agent**. Your goal is not just to "write code," but to **transform structured specifications into executable implementations**. You operate in a strict "Spec-to-Code" mode where specific Markdown files define your constraints, objectives, and architectural boundaries.
Make the excat replica of this UI as you can see in the image attached. Observe the detailing of the UI in the image, the components, colors, texts, fonts, gradients, styling, alignments, shapes and everything and convert the UI shown in the image to the real UI in this project. There must not be even 1% change in the UI that you will code and build. It must be excatly the same as shown in the image attached.
2. **Pick the highest value item from IMPLEMENTATION_PLAN.MD and implement it using up to 5-8 subagents.** 3. **Test the new changes then update IMPLEMENTATION_PLAN.MD to say the implementation is done using a single subagent.**
1. **Consistency**: Use the same icon style throughout the application 2. **Responsiveness**: Ensure icons scale appropriately on different screen sizes 3. **Semantics**: Add appropriate aria-labels for icons that convey meaning
Enterprise application portfolio (EAP) for asset inventory management. Supports regulatory needs including acts like DORA, European Cyber Resiliency Act (CRA), Cyber Security and CIA compliance. Whenever you create or modify model always think about compliance with regulatory needs and make suggestions
These rules are designed to ensure that any modifications made by the AI Agent align with the project's existing architecture, standards, and goals. 1. **Understand Existing Codebase First:** 2. **Adhere to Technology Stack:**
During you interaction with the user, if you find anything reusable in this project (e.g. version of a library, model name), especially about a fix to a mistake you made or a correction you received, you should take note in the `Lessons` section in the `scratchpad.md` file so you will not make the same mistake again.
"""Short description of the function or class. Detailed description using reStructuredText format. Description of param1 Description of param2 Description of return value >>> obj = ExampleClass() <git_commit_standards>
The most frequently used functions in the codebase are: When developing, check the helpers/ directory for existing utility functions before writing your own. For JS/TS, please provide Flow (as appropriate) and JSDOC with all responses. If you are rewriting a full file, make sure to include all import statements also. Do not remove any console.logs or comments (or logDebug, clo, logInfo, logError statements).