Feature module pattern organizing domain logic into queries, mutations, and actions. Use when implementing data fetching with filters, API mutations with loading states, business logic with UI feedback, or organizing domain-specific code.
/plugin marketplace add leeovery/claude-nuxt/plugin install leeovery-claude-nuxt@leeovery/claude-nuxtThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/actions.mdreferences/mutations.mdreferences/queries.mdDomain-based feature modules with three-layer pattern: queries, mutations, actions.
queries.md - Reactive data fetching with filters mutations.md - Pure API operations with loading states actions.md - Business logic with UI feedback
Component → Action → Mutation → Repository → API
↓
Query (reactive data fetching)
features/{domain}/
├── queries/
│ ├── get-posts-query.ts # List with filters
│ └── get-post-query.ts # Single item
├── mutations/
│ ├── create-post-mutation.ts
│ ├── update-post-mutation.ts
│ └── delete-post-mutation.ts
└── actions/
├── create-post-action.ts
├── update-post-action.ts
└── delete-post-action.ts
Query - Reactive data fetching:
export default function getPostsQueryFactory() {
const postApi = useRepository('posts')
return (filters: MaybeRef<GetPostsFilters>) => {
return useFilterQuery('posts', () => postApi.list(params), filters)
}
}
Mutation - Pure API call:
export default function createPostMutationFactory() {
const postApi = useRepository('posts')
const { start, stop, waitingFor } = useWait()
return async (data: CreatePostData) => {
start(waitingFor.posts.creating)
try { return (await postApi.create(data)).data }
finally { stop(waitingFor.posts.creating) }
}
}
Action - Business logic + UI:
export default function createPostActionFactory() {
const createPost = createPostMutationFactory()
const flash = useFlash()
return async (data: CreatePostData) => {
const post = await createPost(data)
flash.success('Post created!')
return post
}
}
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.