Cursor rule Cursor
Do not add Cursor IDE lines to git commit messages (Made-with, Co-authored-by).
MCP server and Cursor plugin that runs software delivery as named, gated steps — skills, agents, rules, and pn-core:// resources.
Cursor rule Cursor
Do not add Cursor IDE lines to git commit messages (Made-with, Co-authored-by).
Cursor rule
MCP-only bootstrap — load pn-core build gate and proactive rules via MCP so flows work without installing the plugin. Copy this file into the workspace you have open in Cursor (your project's .cursor/rules/), not into the pnCore repo.
Cursor rule
Non-generic UI baseline for user-facing surfaces; aligns with .pncore-design.md and pn-core aesthetics reference when MCP is available.
Cursor rule
Use AGENTS.md for preferences and workspace facts; verify with live reads before consequential actions.
Cursor rule
Astro conventions: islands, SSG, client directives. Use when editing .astro files. For React components used as Astro islands, pn-react also applies.
Cursor rule
Babylon.js scene structure, disposal, and performance. Use when editing Babylon.js or 3D scene code.
Cursor rule
Blender scripting conventions: Python style for bpy, no absolute paths, consistent naming, Geometry Nodes scripting, extension manifest. Use when editing Blender Python scripts, add-ons, or Geometry Nodes setups.
Cursor rule
For build/design/scaffold requests, load pn-build or pn-design; discovery and skeptic mandatory. For fix/tweak, use skills directly.
Cursor rule
CI/CD workflow and YAML conventions. No hardcoded secrets; use platform secrets. Use when editing GitHub Actions or GitLab CI.
Cursor rule
Concise agent chat — lead with the answer, ban hedging/slop, scope lock, response aliases (scr/eli/foc/ref/scp). Use when responses are verbose, user asks to compress, or those aliases appear.
Cursor rule
Use an explicit current date for changelogs, "as of" lines, and time-sensitive claims; prefer MCP health UTC fields when the server is connected.
Cursor rule
Design system rule: enforces token usage when editing CSS, SCSS, or styled components. Use tokens for color, spacing, typography; avoid one-off values. For establishing or auditing a design system, use the pn-design-system skill.
Cursor rule
Diagram quality for markdown, HTML, and Mermaid sources — deletion, type pick, brand tokens; load pn-diagram-design.
Cursor rule
When planning or scaffolding, ensure discovery spec exists and is referenced. Security and design decisions must be documented before implementation.
Cursor rule
Figma design-to-code conventions: token extraction, component mapping, naming alignment. Use when implementing designs from Figma or maintaining design-code sync.
Cursor rule
Go backend style, env, and error handling. Use for API and server code (Gin, Fiber, Echo).
Cursor rule
Godot 4.x coding conventions: GDScript typing, signal patterns, scene composition, shader style, naming, Resource patterns, multiplayer RPC safety, GDExtension registration. Use when editing .gd, .tscn, .tres, .gdshader, or project.godot files.
Cursor rule
When MCP is available, use pn-core tools proactively when tasks match pn skills or agents; use Octocode for code research when available.
Cursor rule
n8n workflow safety and patterns. No secrets in workflow JSON; use credentials and env. Use when editing n8n workflows or workflow JSON.
Cursor rule
Next.js best practices. Data loading, server/client boundaries, streaming, mutations, and performance. For Next app/ or pages/, pn-react also applies (core React patterns); content is complementary.
Cursor rule
Node.js and backend style, safety, and env/secrets. Use for API and server code.
Cursor rule
Orchestrator-lead mode for workflowstep — tier-first delegation when lead is longhorizon or premium+parallel.
Cursor rule
PHP backend style, env, and error handling. Use for API and server code (Laravel, Slim).
Cursor rule
Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.