SkillAgentSearch skills...

awesome-ai-rules

🤖 Curated AI coding assistant rules for Cursor, Claude Code, Copilot, Windsurf, Codex CLI & Gemini CLI. Copy-paste configs for TypeScript, React, Next.js & Python.

Install / Use

npx skills add Lay4U/awesome-ai-rules

Installs into whichever agent you are using.

About this skill
🏄

.windsurfrules

Windsurf/Codeium rules

Quality Score

53/100

Supported Platforms

Windsurf

Our assessment of awesome-ai-rules

awesome-ai-rules scores 53/100 on our quality scale, 4217th of 4,595 Development & Engineering skills we index.

Its .windsurfrules is 1.9 KB long, well organised into 9 sections and no code examples: moderately detailed.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
20/30
Structure
13/20
Description
15/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-10-19 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

awesome-ai-rules compared with similar skills

All 4 of these similar skills score higher than awesome-ai-rules; compare them before choosing.

SkillScoreStarsUpdatedFormat
awesome-ai-rules (this skill)by Lay4U530—.windsurfrules
taste-skillby Leonxlnx100101.7k3d agoCLAUDE.md
Agent-Reachby Panniantong100101.4ktodayCLAUDE.md
headroomby headroomlabs-ai10077.7ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10064.2k3d agoCLAUDE.md

Frequently asked questions

How do I install awesome-ai-rules?
Run npx skills add Lay4U/awesome-ai-rules. The install tabs above show the steps for each supported agent.
Which AI agents does awesome-ai-rules work with?
It is written for Windsurf, as a .windsurfrules file. Other agents that read the same format can often use it too.
Is awesome-ai-rules safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is awesome-ai-rules still maintained?
We could not determine when the repository was last updated.

Windsurf Rules: Rust

Baseline

  • Produce Rust that is safe by default and simple to audit.
  • Prefer clear data flow over clever abstractions.

Borrowing and Lifetimes

  • Start with borrowed references before choosing ownership transfer.
  • Limit mutable access windows to reduce borrow conflicts.
  • Make lifetimes explicit when signatures are ambiguous.
  • Do not patch borrow errors with broad cloning.

Error Strategy

  • Use Result<T, E> for all recoverable failures.
  • Use thiserror for reusable library error enums.
  • Use anyhow for app-level glue code and command entrypoints.
  • Add contextual details at I/O, parsing, and network boundaries.
  • Disallow unwrap() in production code.
  • Prefer ?; use expect() only with clear invariant text.

Matching and Control Flow

  • Keep pattern matching exhaustive and intentional.
  • Avoid _ arms on domain enums unless future variants are truly irrelevant.
  • Use let ... else for early exits and reduced nesting.

Workspace and Quality Gates

  • Structure multi-crate projects as Cargo workspaces.
  • Keep shared crates framework-agnostic.
  • Format with cargo fmt --all.
  • Lint with cargo clippy --all-targets --all-features -D warnings.
  • Treat lint suppressions as exceptions requiring comments.

Unsafe Policy

  • Use unsafe only when benchmarked or API-constrained.
  • Encapsulate unsafe internals in small modules.
  • Add safety comments that state required invariants.
  • Validate unsafe assumptions with targeted tests.

Testing and Docs

  • Run cargo test --workspace before finishing.
  • Put integration tests in tests/.
  • Keep unit tests close to the module they verify.
  • Provide rustdoc on public APIs with short examples.
  • Ensure doc examples are accurate and compilable.

Implementation Style

  • Prefer iterator chains to manual indexing loops.
  • Keep functions small, typed, and single-purpose.
  • Favor explicit domain enums over stringly typed status values.

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low