flowai-skill-engineer-rule

Create persistent AI rules for Cursor, Claude Code, and OpenCode environments.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/korchasa/foxcode --skill flowai-skill-engineer-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowai-skill-engineer-rule
Source: https://github.com/korchasa/foxcode/tree/main/.claude/skills/flowai-skill-engineer-rule
Command: npx skills add https://github.com/korchasa/foxcode --skill flowai-skill-engineer-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill guides through creating persistent rules — instructions that automatically apply to AI agent sessions, enforcing coding standards, project conventions, and file-specific patterns across multiple IDEs.

Core Features & Use Cases

  • Rules are Markdown files with metadata that provide persistent context to AI agents and are automatically injected into relevant sessions.
  • Supports two primary modes: always-apply rules that persist across all sessions, and conditional rules triggered when matching files are open.
  • IDE-agnostic guidance includes Cursor, Claude Code, and OpenCode placement strategies, rule templating, and frontmatter conventions.

Quick Start

Create a new persistent rule named flowai-skill-engineer-rule that enforces coding standards across all IDEs.

Frequently Asked Questions about flowai-skill-engineer-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create persistent AI coding rules that automatically apply across different IDEs?

Persistent AI rules are created as Markdown files with metadata that provide persistent context to AI agents and are automatically injected into relevant sessions to enforce coding standards across Cursor, Claude Code, and OpenCode.

What is the difference between always-apply and conditional rules for AI agents?

Always-apply rules persist across all sessions, while conditional rules are triggered when matching files are open, ensuring file-specific patterns are enforced contextually without manual intervention.

How do I set up project conventions and frontmatter validation for Cursor and Claude Code?

You set up project conventions by applying IDE-specific placement strategies for rule files with frontmatter validation, enabling Cursor, Claude Code, and OpenCode to automatically enforce project conventions.

Does this approach work for enforcing file-specific patterns without manual prompting?

Yes, conditional rules automatically enforce file-specific patterns by matching open files and injecting relevant instructions into the AI agent session without requiring manual prompting during coding.

What's the best way to manage rule templates and IDE-specific placement for AI coding standards?

The best way to manage rule templates is using IDE-agnostic guidance for placement strategies, ensuring rule files with frontmatter conventions are correctly structured for Cursor, Claude Code, and OpenCode.

When should I not use always-apply rules for AI agent sessions?

You should not use always-apply rules when enforcing file-specific patterns, as they persist across all sessions; conditional rules are better suited for contextual enforcement triggered by matching open files.