Windsurf & Cline Rules
Rules files for Windsurf and Cline editors
Showing 61–120 of 128 skills · Page 2 of 3
ahmetvural01 / 03-agent-policy
Demo deployment for clinic management platform
ahmetvural01 / 01-multitenancy
Demo deployment for clinic management platform
Lay4U / .clinerules
🤖 Curated AI coding assistant rules for Cursor, Claude Code, Copilot, Windsurf, Codex CLI & Gemini CLI. Copy-paste configs for TypeScript, React, Next.js & Python.
Angular-Material-Dev / angular-material-ai-rules
13This repo contains rules, instructions and guidelines for various AI based code editors to work with Angular Material
AdriDob / context
OWNEX — Autonomous Work Operating System: opportunity discovery, security automation, agent orchestration, local-first AI routing, revenue intelligence. Python/FastAPI + Vue 3 + Tauri.
AdriDob / orion-rules
OWNEX — Autonomous Work Operating System: opportunity discovery, security automation, agent orchestration, local-first AI routing, revenue intelligence. Python/FastAPI + Vue 3 + Tauri.
noriaki / linting-workflow
When working with code that has linting or type errors, follow this specific workflow: 1. **First attempt automatic fixes**
Themis128 / 10-ai-agent-rules
- **Direct and technical:** Be direct and technical in responses — no conversational filler ("Great", "Certainly", "Okay", "Sure") - **One tool at a time:** Wait for user confirmation after each tool use before proceeding - **Verify before completing:** Check task requirements, verify output files e…
Themis128 / 08-workflow-rules
- **Branch strategy:** Feature branches from `main`, PRs to `main` - **Commit messages:** Conventional commits format: `type(scope): description` - Types: `feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `style`, `ci`
Themis128 / 03-coding-standards
- **TypeScript:** Strict mode enabled. Prefer `interface` over `type` for object shapes. Use `type` for unions, intersections, and utility types. - **React:** Use functional components with hooks. Server Components by default; add `'use client'` only when interactivity is needed.
Cyptopimpinainteazy / 00-x3-core-rules
Establishes the foundational operating law for all coding sessions. Every agent must follow these rules before, during, and after producing code. - Inspect actual source files, not just markdown docs, before making claims.
Cyptopimpinainteazy / 02-no-fake-completion
Prevent agents from using stubs, mocks, no-ops, or placeholder logic and calling them "implemented." - When you write a function body, it must contain real logic, not a stub.
Cyptopimpinainteazy / 03-production-code-only
All code merged into main must be production-quality. No demo paths, mock backends, hardcoded test addresses, or in-memory-only persistence should be shipped to production. - Prefer production-quality implementations over demo/mock versions.
Cyptopimpinainteazy / 04-runtime-wiring-required
A file existing in the repo does not mean it is wired into the runtime. Code must be reachable from the actual execution path. - Before claiming a module/feature is "wired", trace it from the entry point (main.rs, lib.rs, CLI, API handler, pallet construct_runtime!).
Cyptopimpinainteazy / 06-security-rollback-required
Every production feature must consider security, rollback, replay, and failure paths before being called complete. - Auth checks must be real, not `return Ok(())` pass-throughs.
electricpants01 / daily-sprint-prompt
Work through this systematically, validating at each checkpoint before moving to the next step. - Find the active sprint for project CHRIS - Get the highest-priority unstarted ticket (by rank/priority field) - Read full ticket details: key, summary, description, acceptance criteria,
tsongglod123 / coding-conventions
This project is fully written with AI
LucasSantana-Dev / ai-dev-toolkit-pt-br
AI Dev Toolkit em português — regras, skills e configurações para Claude Code, Cursor e Windsurf
AK2083 / windows-dev-setup
Windows developer setup — VC++ Redistributable for native Node addons (npm test / electron:start)
noriaki / code-quality
Always follow this process when making code changes: 1. After writing or modifying code, run the following checks in order:
Meeovi / nuxt-search
Stable entrypoint for generated Nuxt guidance in this repository. Use for Nuxt SSR, hydration, pages, `runtimeConfig`, Nitro/h3, plugins, Nuxt UI, Nuxt Content, or Nuxt module work. If generated content is missing, regenerate it with `nuxt prepare`.
Meeovi / nuxt-meeovi-frontend
Stable entrypoint for generated Nuxt guidance in this repository. Use for Nuxt SSR, hydration, pages, `runtimeConfig`, Nitro/h3, plugins, Nuxt UI, Nuxt Content, or Nuxt module work. If generated content is missing, regenerate it with `nuxt prepare`.
devhax-heavy-industries / markdown.instructions
Documentation and content creation standards
Themis128 / 09-mcp-rules
The project uses the following MCP servers:
semaj90 / 20-validation
legal ai contextual chat
Themis128 / 01-project-overview
A Next.js 16 + Cloudflare Workers full-stack application for cloud consulting services.
Cyptopimpinainteazy / 01-proof-before-claim
No completion claim is valid without proof from actual source, tests, wiring, and command output. - Before saying anything is "done", run the strongest proof command available.
Cyptopimpinainteazy / 07-cross-vm-atomic-rules
Cross-VM operations (EVM, SVM, BTC, CosmWasm, X3VM) must be atomic or have proven rollback. Partial execution across chains is an invariant violation. - Every cross-chain transfer must have a timeout and refund path.
Cyptopimpinainteazy / 08-status-report-required
Every response must communicate actual completion status with an honest status bar. No hiding behind vague language. - Include a status bar with 10-block visual bars for Overall, Code, Tests, Wiring, Docs, and Proof.
Cyptopimpinainteazy / 09-next-10-tasks-required
Every completion report must include exactly 10 concrete next tasks. This prevents agents from abandoning work with no clear path forward. - List exactly 10 tasks, numbered 1 through 10.
semaj90 / 30-svelte
legal ai contextual chat
semaj90 / 10-architecture
legal ai contextual chat
iging / 00-agent-spec
A tool-agnostic behavioral specification for AI coding agents. Define how agents discover instructions, resolve conflicts, make engineering decisions, and report their work using portable Markdown files.
iging / 50-project-facts
A tool-agnostic behavioral specification for AI coding agents. Define how agents discover instructions, resolve conflicts, make engineering decisions, and report their work using portable Markdown files.
iging / 10-anti-hallucination
A tool-agnostic behavioral specification for AI coding agents. Define how agents discover instructions, resolve conflicts, make engineering decisions, and report their work using portable Markdown files.
zozo123 / harness
One prompt, three contradictory biographies: a satirical field report about free AI and confident hallucinations.
BryanHarrisScripts / 00-plotpickle
`AGENTS.md` at the repository root is the canonical PlotPickle development contract. Read and follow it before planning or editing. Cline-specific guardrails: - Work on a branch or isolated worktree, never directly on `main`.
Ossamoon / _basic
Deno CLI Tool for summarizing and processing musicXML files.
semaj90 / 00-project-contract
legal ai contextual chat
devhax-heavy-industries / review.instructions
Guidelines for writing Tailwind in Typescript React Apps
devhax-heavy-industries / tailwind.instructions
Guidelines for writing Tailwind in Typescript React Apps
AK2083 / legal-open-source
Legal and privacy baseline context for every implementation
eduardo-sl / .clinerules
Curated AI agent skills for Go projects.
char5742 / 00_basic
ユーザーはRooよりプログラミングが得意ですが、時短のためにRooにコーディングを依頼しています。 2回以上連続でテストを失敗した時は、現在の状況を整理して、一緒に解決方法を考えます。 私は GitHub
Nlkomaru / coding
oklch-based color palette and semantic token generator for design systems.
Nlkomaru / about-projects
oklch-based color palette and semantic token generator for design systems.
tsongglod123 / project-context
This project is fully written with AI
noriaki / 00_basic
ユーザはプログラミングが得意ですが、時短のために私にコーディングを依頼しています。 2回以上連続でテストを失敗した時は、現在の状況を整理して、一緒に解決方法を考えます。 私は GitHub から学習した広範な知識を持っており、個別のアルゴリズムやライブラリの使い方はユーザが実装するよりも速いでしょう。テストコードを書いて動作確認しながら、ユーザに説明しながらコードを書きます。
asshat1981ar / 00-recon
Before editing, identify entry points, relevant tests, configuration, and local conventions. Prefer targeted searches and read only files needed for the task.
asshat1981ar / 10-safety
Respect requested scope. Never run destructive commands such as reset --hard, clean -fd, force push, or recursive deletion without explicit approval. Do not expose secrets.
asshat1981ar / 30-context
Use progressive skills for detailed procedures. Keep plans and evidence compact, and preserve decisions, open risks, and test results when context is compacted.
asshat1981ar / 20-verification
Every change must be checked with the narrowest relevant formatter, type checker, test, or build. Report commands and failures honestly.
AK2083 / auth-security
Security rules for local users, roles, sessions and access requests
AK2083 / sync-security
Security rules for synchronization with Supabase or remote services
mormorbump / 00_basic
fsmによる状態遷移のサンプル
nimiusrd / business_logic
ビジネスロジックの実装方法とテスト方法に関するガイドライン
mizchi / 00_basic
ユーザーはRooよりプログラミングが得意ですが、時短のためにRooにコーディングを依頼しています。 2回以上連続でテストを失敗した時は、現在の状況を整理して、一緒に解決方法を考えます。 私は GitHub
Nlkomaru / 00_basic
oklch-based color palette and semantic token generator for design systems.
kyouyap / 00_basic
ユーザーはRooよりプログラミングが得意ですが、時短のためにRooにコーディングを依頼しています。 2回以上連続でテストを失敗した時は、現在の状況を整理して、一緒に解決方法を考えます。 私は GitHub
AK2083 / security-privacy
Security and privacy rules for implementations