Rules

This document outlines best practices and coding standards for developing applications with Spring Boot. Following these guidelines will help ensure that your applications are robust, maintainable, performant, and secure.

1. Unless it's necessary or told otherwise, try reusing existing files, both for implementation and tests. 2. If possible, try running relevant tests.

Activate the Technical Writer persona by following the agent definition below. This rule provides specialized development assistance for technical writer-related tasks.

Cursor IDE rules and conventions for AI-assisted development.

You are an AI assistant with advanced problem-solving capabilities. This file defines only the behaviors for maximizing productivity and safety in **code-centric tasks**. This file serves as the foundation rules for executing coding-related tasks.

Cursor IDE rules and conventions for AI-assisted development.

Typical commit order: 1. mechanical / scaffolding (only if needed) 2. generated code updates (if any, separate) 3. refactors that enable the change (separate from behavior changes) 4. feature implementation

Adapted from [github/awesome-copilot go.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/go.instructions.md), extended with AI agent, Eino framework, and LLM provider conventions.

This rule is triggered when the user types `@qa` and activates the QA Specialist agent persona.

<critical_known_issues> </critical_known_issues> Before touching any file, follow this sequence: 1. READ the relevant spec in specs/ 2. PLAN — update tasks/ACTIVE.md with what you're doing 3. BUILD — smallest meaningful increment

This rule is triggered when the user types `@sm` and activates the Scrum Master agent persona.

Cursor IDE rules and conventions for AI-assisted development.

Every page must start with frontmatter: title: "Clear, specific title" description: "Concise description for SEO and navigation"

Welcome to the OpenLoom project. This document is the entry point for AI assistants to understand how to interact with this codebase.

These rules are **prescriptive**. Every interaction MUST follow them. They combine real codebase patterns with approved architectural decisions.

This document outlines the key rules and principles for developing and maintaining the Portfolio Scraper project.

This rule is triggered when the user types `@ux-expert` and activates the UX Expert agent persona.

This rule is triggered when the user types `@po` and activates the Product Owner agent persona.

This rule is triggered when the user types `@dev` and activates the Full Stack Developer agent persona.

**MISSION**: Build ACT (Agent Coordination Transfer) - autonomous multi-agent coordination infrastructure in 1.5 days for hackathon demo.

Cursor IDE rules and conventions for AI-assisted development.

All API responses MUST follow this structure.