superpowers-plus / rules
Cursor rule8 starsChanged 3 days agoMITView on GitHub
javascript rules
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository134 other files it gives its agents.
- AGENTS.mdAGENTS.md
- guidance/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- guidance/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/cli-tools.mdcCursor rule
- .cursor/rules/invariants.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/shell.mdcCursor rule
- blast-radius-checkSkill
- brainstormingSkill
- branch-flow-gateSkill
- branch-sync-gateSkill
- codebase-reconSkill
- codeowners-drift-auditSkill
- code-review-batterySkill
- cognitive-complexity-refactoringSkill
- debateSkill
- debug-conductorSkill
- dispatching-parallel-agentsSkill
- domain-buildSkill
- evidence-adjudicatorSkill
- executing-plansSkill
- external-cli-auditSkill
- feature-developmentSkill
- field-rename-verificationSkill
- finishing-a-development-branchSkill
- git-branch-conventionsSkill
- gitlab-cliSkill
- hotfix-charterSkill
- implementation-trackerSkill
- incident-revert-reviewSkill
- infra-config-investigatorSkill
- investigation-stateSkill
- kernel-splitSkill
- llm-behavior-investigatorSkill
- llm-skill-reviewSkill
- merge-authorization-gateSkill
- micro-harsh-reviewSkill
- output-verificationSkill
- pre-commit-gateSkill
- progressive-code-review-gateSkill
- progressive-harsh-reviewSkill
- providing-code-reviewSkill
- pr-triage-gateSkill
- push-authorization-gateSkill
- receiving-code-reviewSkill
- reproduction-experiment-investigatorSkill
- requesting-code-reviewSkill
- requirements-validation-pmSkill
- requirements-validationSkill
- scope-tripwireSkill
- session-handoffSkill
- skills-hierarchy-tuningSkill
- sp-bughuntSkill
- state-consistency-investigatorSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- timeline-trace-investigatorSkill
- The first 60 shown.
The file
We split this javascript.mdc into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 92
NEVER defer linting fixes.
- Distinctive: line 116
Check every link - verify navigation
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description: javascript rules
globs: "**/*.{js,ts,jsx,tsx}"
alwaysApply: false
---
# JavaScript/TypeScript Coding Conventions
> **Priority**: HIGH - Apply to all JS/TS projects
> **Source**: genesis, architecture-decision-record, strategic-proposal AGENTS.md
## Code Quality Requirements
- **Linting**: ESLint (9.x flat config preferred)
- **Coverage**: ≥85% minimum, 90%+ target
- **Formatting**: Consistent style enforced by config
## Style Variations
**Note**: Quote style varies by project. Check existing code:
```javascript
// genesis-tools pattern (single quotes)
const message = 'Hello, world';
// Other projects may use double quotes
const message = "Hello, world";
```
Common conventions:
- **Indentation**: 2 spaces
- **Semicolons**: Required
- **Trailing commas**: ES5-compatible (arrays, objects)
## ESLint 9.x Flat Config
```javascript
// eslint.config.js
import js from '@eslint/js';
import globals from 'globals';
export default [
js.configs.recommended,
{
languageOptions: {
globals: { ...globals.browser, ...globals.node }
},
rules: {
'no-unused-vars': 'error',
'no-console': 'warn'
}
},
{
// Use a **/ prefix so nested directories match
ignores: ['**/node_modules/**', '**/dist/**', '**/build/**']
}
];
```
## Testing Patterns
```javascript
describe('Processor', () => {
describe('process()', () => {
it('should handle valid input', () => {
const result = processor.process('input');
expect(result).toBe('expected');
});
it('should throw on invalid input', () => {
expect(() => processor.process(null)).toThrow();
});
});
});
```
## Commands
```bash
# Lint
npm run lint
# Test with coverage
npm test -- --coverage
# Security scan
npm audit
```
## ⚠️ Fix Linting Issues Immediately
NEVER defer linting fixes. Fix them before committing.
---
## UI/Web Application Patterns
> Source: genesis-tools AGENTS.md
### Click handlers
Give each clickable element a working event handler.
```javascript
// ✅ CORRECT - event handler attached
button.addEventListener('click', handleSubmit);
// ❌ WRONG - element exists but does nothing
const button = document.createElement('button');
// No event handler = stillborn element
```
**Before claiming UI work complete:**
1. Click every button - verify response
2. Submit every form - verify processing
3. Check every link - verify navigation
### UI Workflow Principles
1. **Never assume linear behavior** - Users skip steps, go back, refresh
2. **State survives refresh** - Save to storage, restore on load
3. **Errors are visible** - Show user-facing messages, not console.log
4. **Loading states exist** - Show spinners during async operations
### Dark Mode Requirements
For web tools requiring dark mode:
```css
:root {
--bg-primary: #1a1a2e;
--text-primary: #eee;
--accent: #4a90d9;
}
body {
background: var(--bg-primary);
color: var(--text-primary);
}
```
### Clipboard Operations Pattern
```javascript
// ✅ CORRECT - throw on error, user sees failure
async function copyToClipboard(text) {
try {
await navigator.clipboard.writeText(text);
showNotification('Copied!');
} catch (err) {
showNotification('Copy failed - check permissions', 'error');
throw err; // Don't silently fail
}
}
```
<!-- golden-agents:generated -->
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

