Instruction file imported from kasuken/pulsedesk (.github/instructions/pulsedesk-branding.instructions.md). Copyright stays with the author.

PulseDesk Branding

Name: PulseDesk Branding
Author: kasuken

Use PulseDesk as the product name in code, docs, UX copy, issues, PRs, and planning notes.
Treat pulsedesk as the preferred repository name and PulseDesk as the preferred solution name.
Default tagline: Your Windows machine, explained.
Keep the core positioning consistent: PulseDesk is a native, local-first, lightweight Windows system health dashboard that shows what the machine is doing and why it feels slow.
Frame the first release around real-time visibility into CPU, RAM, GPU, disk, network, temperatures, and system bottlenecks.
Prefer language that is professional and approachable for developers, IT admins, and power users. Avoid overly gamer-centric, vendor-specific, or unnecessarily nerdy branding.
When drafting alternative short copy, prefer variants aligned with these messages: Know what your PC is doing., Real-time system health for Windows., A cleaner way to understand your PC performance.
When proposing a broader repo layout, prefer this structure unless the user asks otherwise:

PulseDesk.sln
src/
  PulseDesk.App/
  PulseDesk.Telemetry/
  PulseDesk.Analysis/
  PulseDesk.Storage/
  PulseDesk.Tray/
tests/
  PulseDesk.Telemetry.Tests/
  PulseDesk.Analysis.Tests/
docs/
  architecture.md
  product-spec.md

{ "ocm": "1", "id": "kasuken-pulsedesk-pulsedesk-branding-instructions", "kind": "skill", "name": "PulseDesk Branding", "description": "Use when naming the product, writing user-facing copy, proposing repo or solution names, restructuring the app into projects, or describing PulseDesk in docs, prompts, issues, PRs, and store listing text. Covers branding, positioning, tagline, and preferred project layout.", "publisher": "kasuken", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when naming the product, writing user-facing copy, proposing repo or solution names, restructuring the app into projects, or describing PulseDesk in docs, prompts, issues, PRs, and store listing text. Covers branding, positioning, tagline, and preferred project layout." ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/kasuken/pulsedesk", "path": ".github/instructions/pulsedesk-branding.instructions.md", "ref": "6f337f23cea258aa18964baff9ee1dac868217a6", "url": "https://github.com/kasuken/pulsedesk/blob/6f337f23cea258aa18964baff9ee1dac868217a6/.github/instructions/pulsedesk-branding.instructions.md", "key": "kasuken/pulsedesk/.github/instructions/pulsedesk-branding.instructions.md" } }, "instructions": "# PulseDesk Branding\n\n- Use `PulseDesk` as the product name in code, docs, UX copy, issues, PRs, and planning notes.\n- Treat `pulsedesk` as the preferred repository name and `PulseDesk` as the preferred solution name.\n- Default tagline: `Your Windows machine, explained.`\n- Keep the core positioning consistent: PulseDesk is a native, local-first, lightweight Windows system health dashboard that shows what the machine is doing and why it feels slow.\n- Frame the first release around real-time visibility into CPU, RAM, GPU, disk, network, temperatures, and system bottlenecks.\n- Prefer language tha", "cost": { "context_tokens": 324 } }

PulseDesk Branding

About

PulseDesk Branding

Use it

Manifest

Reviews