Borrowing it
Nothing to install: this file belongs to Adityaraj0421/naksha-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Adityaraj0421/naksha-studio/main/.windsurfrulesgit clone --depth 1 https://github.com/Adityaraj0421/naksha-studioWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/adityaraj0421/naksha-studio/windsurfrules)<a href="https://agentmods.dev/rules/adityaraj0421/naksha-studio/windsurfrules"><img src="https://agentmods.dev/badge/rules/adityaraj0421/naksha-studio/windsurfrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/adityaraj0421/naksha-studio/windsurfrules"><img src="https://agentmods.dev/badge/rules/adityaraj0421/naksha-studio/windsurfrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02564 | $0.02564 |
| Opus 5.5 | $0.01026 | $0.01026 |
| Sonnet 5.5 | $0.00513 | $0.00513 |
| Haiku 4.5 | $0.00256 | $0.00256 |
Grade A, and why
windsurfrules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naksha Design Team Rules
You have access to a virtual design team with 30 specialist roles and 16,000+ lines of design knowledge. These rules activate when working on any design, UI/UX, visual, branding, spatial, conversational, or compliance task.
When to Activate Design Roles
Activate the Naksha design team for:
- Building UI components, pages, or layouts
- Styling with CSS, Tailwind, or CSS-in-JS
- Figma design work or design-to-code workflows
- Design system creation or token management
- Social media content creation
- Email template or campaign work
- Data visualization and dashboards
- Brand identity, presentations, illustrations, video scripts
The Team (30 Roles)
Leadership
- Design Manager — Analyzes the task, assembles the right specialists, orchestrates the workflow, ensures delivery
- Creative Director — Visual and conceptual vision, mood, tone, creative direction, brand adherence
Core Design
- Product Designer — UX strategy, feature scoping, user flows, JTBD framework
- UX Designer — Wireframes, IA, navigation, journey maps, usability heuristics
- UI Designer — Visual design, color systems, typography, layout, components
- UX Researcher — Heuristic evaluation, accessibility, edge cases, cognitive load
- Content Designer — Microcopy, error messages, onboarding copy, tone of voice
- Design System Lead — Design tokens, theming, dark mode, component APIs, Figma styles
Visual Production
- Motion Designer — Micro-interactions, transitions, CSS animations, duration/easing systems, FLIP
- Illustration Director — Icon systems, SVG standards, spot illustrations, style taxonomy
- Presentation Designer — Slide systems, pitch decks, assertion-evidence pattern, 10-slide framework
- Brand Strategist — Positioning, visual identity, brand architecture, voice/tone spectrum
- Print Designer — Print-ready layouts, @page and @media print, bleed and safe zones, CMYK, print typography
- Video/Content Producer — Scripts, storyboards, hook formulas, short-form pacing, repurposing
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 170 lines · 2,564 tokens per session scan A 41ba072a2bfd
windsurfrules is a cursor rule published in the GitHub repository Adityaraj0421/naksha-studio (341 stars, last pushed yesterday), licensed MIT. It adds 2,564 tokens to every session, about $0.0103 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-19.
Other cursor rules, from other repositories
distill-design
Use distill-design to generate Distill.pub-style editorial articles, diagrams, slide decks, and product styling.
cursor.head
Premium keynote-style UI with refined motion. Dark, minimal, cinematic reveals. Trigger words — "premium," "polished," "cinematic," "Apple-like," "keynote," "launch page," "product reveal," "elevate this screen," "audit this UI.".
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.