Use when adding state management to a module - creates Svelte store with server state integration.
Scanned 6/7/2026
Install via CLI
openskills install NoaiRox/specialist-agent---
name: dev-create-store
description: "Use when adding state management to a module - creates Svelte store with server state integration."
user-invocable: true
argument-hint: "[store-name]"
allowed-tools: Read, Write, Edit, Bash, Glob, Grep
---
Create a Svelte store following `docs/ARCHITECTURE.md` section 4.4.
Store: $ARGUMENTS
## Steps
1. Read `docs/ARCHITECTURE.md` section 4.4.
2. Determine the type:
- **writable/readable store** -- for simple state (filters, toggles, preferences)
- **Rune-based class** -- for state with derived values and multiple methods
3. Choose placement:
- Module-specific -> `src/lib/modules/[feature]/stores/[name]-store.ts`
- Shared -> `src/lib/shared/stores/[name]-store.ts`
4. Create the store:
### Option A: writable/readable store
```typescript
// stores/[name]-store.ts
import { writable, derived } from 'svelte/store'
function createXxxStore() {
const someState = writable<string | null>(null)
const isActive = writable(false)
const hasSomeState = derived(
[someState, isActive],
([$state, $active]) => !!$state && $active
)
function setSomeState(value: string | null) {
someState.set(value)
}
function reset() {
someState.set(null)
isActive.set(false)
}
return {
someState: { subscribe: someState.subscribe },
isActive: { subscribe: isActive.subscribe },
hasSomeState,
setSomeState,
reset,
}
}
export const xxxStore = createXxxStore()
```
### Option B: Rune-based class
```typescript
// stores/[name]-store.ts
export class XxxStore {
someState = $state<string | null>(null)
isActive = $state(false)
get hasSomeState() {
return !!this.someState && this.isActive
}
setSomeState(value: string | null) {
this.someState = value
}
reset() {
this.someState = null
this.isActive = false
}
}
export const xxxStore = new XxxStore()
```
5. Rules:
- Only client state (UI, filters, preferences, session)
- NO server state (use SvelteKit load functions)
- NO HTTP calls inside stores
- Read-only exposure where possible
6. Validate: `npx svelte-check --tsconfig ./tsconfig.json`
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.