Results for “record-page”

Recover deleted records, analyze freelist pages, WAL files, and unallocated space in SQLite databases for digital forensics and incident response.

Use to review how call recordings are notified, stored, accessed, redacted and deleted, including the parts that differ from text conversations. Trigger for "review our call recording practices", "do we need to tell customers we're recording", "who can listen to our calls", recording retention, card details spoken on a call, or a request for a customer's own recording.

任意のジャンル・テーマで曲＋歌詞を制作する汎用作曲エンジン。曲先（メロディ淘汰型）でキャッチーなサビメロディを複数生成→人間が選別→変奏淘汰で確定→歌詞を載せる、ヒット曲プロセス準拠。作曲・作詞に特化。MiniMax music-2.6 主軸。ユーザーが「曲作って」「作曲して」「音楽作って」「歌作って」「オリジナル曲作って」「新しい曲作って」「武将で曲作って」「サイバー和で曲作って」と言った時、または /make-song を呼んだ時にトリガー。テーマ修飾（武将/サイバー和）は Phase 0 の [THEME] 選択で対応。

Generates a three-column technical documentation page with side navigation, article body, and sticky table of contents.

Prepare Supabase-compatible persistent storage for a dynamic QW Page. Use with qw-pages when a webpage needs database tables, server-side persistence, Supabase access, or database-backed APIs.

Scaffold a new public page under the (public) route group, following project conventions for server components, tenant config, and shadcn/ui styling.

【非推奨 → ssot-record を使うこと】 ssot-record に統合済み。/record-decision が呼ばれた場合は ssot-record スキルに処理を委譲する。

启动当前飞书会话的录音。当用户需要发起录音，或对录音进行中的内容询问的时候，可以使用此技能。

Redis in-memory data store. Covers data structures, caching, and pub/sub. Use for caching and real-time features. USE WHEN: user mentions "redis", "caching", "session storage", "rate limiting", "pub/sub", "sorted sets", "in-memory database", "cache invalidation" DO NOT USE FOR: relational data - use `postgresql` or `mysql` instead, document storage - use `mongodb` instead, full-text search - use `elasticsearch` instead

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Track open comment periods and draft a substantive, on-the-record comment that argues your position within the docket's rules and deadline.

Record polished UI demo videos using Playwright with visible cursor, natural pacing, and storytelling flow.

Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step.

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Save the current diagnosis state to disk for cross-session recall, including conclusions, rejected directions, and next steps.

Use only for video game projects; plan Steam/store page, capsule, trailer, screenshot, tag, and wishlist validation

Record, search, and prune per-project learnings in .claude/learnings.jsonl — typed, confidence-scored, searchable across sessions

Generates a standard admin dashboard page with a fixed sidebar, top bar, KPI card grid, 1-2 charts, and a recent activity list.

Page components — the thin data-fetching layer that binds a route to a template, invoking getServerSideProps/getStaticProps and passing props down. Use when creating a new route, choosing SSR vs SSG vs ISR for a page, or reviewing whether a page is doing template-level work it shouldn't.

Decide whether Git submodules are the right boundary for external dependencies, then execute the appropriate workflow: add and pin, bootstrap recursively, sync to a recorded commit, advance a tracked branch, edit inside a submodule without detached-HEAD surprises, remove cleanly, or configure CI checkout constraints.