Run comprehensive pre-press preflight checks on Adobe Illustrator documents using illustrator-mcp tools. Detects print-critical issues (RGB in CMYK, broken links, low-res images, white overprint, text not outlined), text consistency problems (dummy text, notation variations), and PDF/X compliance. Use when user asks to check a document before printing, submission, or handoff — or mentions "preflight", "pre-press check", "print check", "submission check".
Use when user wants to develop on the SecondMe platform (second.me, develop.second.me). Triggers: building SecondMe third-party apps (第三方应用/外部应用), SecondMe OAuth login integration (Client ID/Secret, token exchange), MCP integration for SecondMe, Agent Memory API, Act stream API, app scaffolding, review submission, or hackathon/黑客松 projects targeting SecondMe. Covers the full developer lifecycle from app creation and credentials to release. NOT for casual SecondMe usage like browsing profiles, adding friends, or social features — only for building and integrating with SecondMe as a developer platform.
Use when users want to bootstrap the brain with existing project knowledge -- reading ADRs, feature specs, UX docs, commit history, and error patterns to seed institutional memory on a project that already has artifacts on disk. Also use for incremental re-hydration after significant work outside the pipeline. Triggers on "hydrate brain", "bootstrap brain", "seed memory", "brain init", "populate brain", "import history".
NVIDIA DeepStream SDK 9.0 development with Python pyservicemaker API. Use when building video analytics pipelines, GStreamer-based video processing, TensorRT inference integration, object detection/tracking, or Kafka/message broker integration.
- 📁 scripts/
- 📁 subskills/
- 📁 templates/
- 📄 .gitignore
- 📄 AGENTS.md
- 📄 CLAUDE.md
Personal AI tutor — generates learning paths, sends daily tasks via Telegram, evaluates progress, and adapts to the learner.
Use when you need to create an academic Beamer presentation with original theme and multi-agent review.
- 📄 .skills-x-meta.json
- 📄 SKILL.md
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- 📁 references/
- 📁 scripts/
- 📄 load-env.sh
- 📄 README.md
- 📄 SKILL.md
Manage code snippets in ByteStash snippet storage service. This skill should be used when the user asks to "save a snippet", "search snippets", "find code", "share snippet", "organize snippets", "list my snippets", "create snippet", "delete snippet", or mentions ByteStash, code storage, snippet management, or code archival.
Command-line interface for the Zengram system. Use this to store, search, and retrieve shared memories from any terminal-based agent or script.
Use this whenever the user asks to "create a module", "scaffold a feature", "add a domain", "new module called X", or starts work on a brand-new vertical (controller + service + repo + model + routes + tests). Duplicates the canonical `modules/tasks` template, applies kebab/Pascal/camel renames, and registers config-driven enums. Module stays self-contained — never modify shared `lib/` or `config/` to bolt on module logic. --- # Create Module Skill Create a new module by copying and renaming the `tasks` template module. ## Prerequisites - The canonical template module `modules/tasks` must exist - You need a name for the new module (kebab-case) ## Steps ### 1. Ask for the module name Prompt user for the new module name in kebab-case (e.g., `my-feature`, `user-settings`) ### 2. Derive naming conventions Follow `/naming` for the full reference. Quick summary from the module name (e.g., `my-feature`): - **kebab-case**: `my-feature` (folder names, file prefixes, routes) - **PascalCase**: `MyFeature` (Mongoose model names, class names) - **lowerCamelCase**: `myFeature` (variable names, function names, JS exports) - **UPPER_SNAKE_CASE**: `MY_FEATURE` (constants) ### 3. Duplicate the module ```bash cp -r modules/tasks modules/{new-module-name} ``` ### 4. Rename references
Use this whenever the user asks to "create a module", "scaffold a feature", "add a Vue domain", "new module called X", or starts work on a brand-new vertical (views + components + store + router entry + tests). Duplicates the canonical `src/modules/tasks` template, applies kebab/Pascal/camel/ UPPER renames, and wires config-driven values. Module stays self-contained. --- # Create Module Skill Create a new module by copying and renaming the `tasks` template module. ## Prerequisites - The canonical template module `src/modules/tasks` must exist - You need a name for the new module (kebab-case) ## Steps ### 1. Ask for the module name Prompt user for the new module name in kebab-case (e.g., `my-feature`, `user-settings`) ### 2. Derive naming conventions Follow `/naming` for the full reference. Quick summary from the module name (e.g., `my-feature`): - **kebab-case**: `my-feature` (folder names, file prefixes, routes) - **PascalCase**: `MyFeature` (component names in JS/templates) - **UPPER_SNAKE_CASE**: `MY_FEATURE` (env keys, constants) - **lowerCamelCase**: `myFeature` (variable names, function names, store exports) ### 3. Duplicate the module ```bash cp -r src/modules/tasks src/modules/{new-module-name} ``` ### 4. Rename references
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
