line-bot-development
Build and maintain LINE messaging API integrations, handle webhook events, and implement bot commands
Discover Databases skills, compare source repositories and read the instructions for each workflow.
Build and maintain LINE messaging API integrations, handle webhook events, and implement bot commands
Design and implement independent per-group configurations for LINE Bot supporting multiple groups simultaneously
Integrate Google Firebase Firestore for cloud data storage, implement CRUD operations, and manage data persistence
Guide for refactoring Python code to follow SOLID principles and improve maintainability
Implement automated scheduling with APScheduler for multi-group timed broadcasts and rotation management
Evaluates the user experience of the bot's command interface and provides actionable recommendations
Deploy Python Flask applications to Railway.app with environment configuration and webhook setup
Basics for using the nab CLI (YNAB tool). Use when asked how to run nab commands, set up authentication tokens/PATs, configure or override the default budget id, or troubleshoot missing NAB_TOKENS/NAB_BUDGET_ID...
Validates Single Source of Truth (SSOT) documentation files for parity with code. Use when user asks about SSOT validation, architecture docs, or project truth sources.
Validates code-documentation parity using tree-sitter static analysis. Use when user asks about documentation validation, doc parity, checking if docs are up to date, or whether code matches documentation.
Create and edit draw.io diagrams in XML format. Use when the user wants to create flowcharts, architecture diagrams, sequence diagrams, or any visual diagrams. Handles XML structure, styling, fonts (Noto Sans J...
Spec Kit を使って要件定義や仕様作成(仕様策定・仕様書作成・仕様設計を含む)を新規作成または既存仕様へ追記し、spec.md/plan.md/tasks.mdまで生成・更新する。要件定義、要件追加/変更、TDD前提の要件整理、仕様の明文化...
Add or update skills in a skills repository for Codex and/or Claude Code. Use when creating new skills, packaging .skill files for Codex, or converting a skill into a Claude Code plugin (marketplace.json + plug...
Inspect GitHub PR for CI failures, merge conflicts, update-branch requirements, reviewer comments, change requests, and unresolved review threads. Create fix plans and implement after user approval. Resolve rev...
Create or update GitHub Pull Requests with the gh CLI, including deciding whether to create a new PR or only push based on existing PR merge status. Use when the user asks to open/create/edit a PR, generate a P...
Ink.js (React for CLI) design and implementation guide. Use when: (1) Creating or modifying Ink.js components (2) Implementing Ink-specific hooks (useInput, useApp, useFocus) (3) Handling emoji/icon width issue...
Use when creating Git commits to ensure they follow the Conventional Commits specification. Provides guidance on commit message structure, types, scopes, and best practices for clear, consistent commit messages...
Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers.
Update the README.md file to list all available journal modules under the Features section. Use when adding, removing, or reorganizing modules and keeping documentation in sync.
Create or update a journal entry module (database, model, actions, views, controllers, API, docs, tests). Use when adding a new journal module or changing an existing module such as mood, health, or obligations...
Create or update an Action in app/Actions following JournalOS conventions (validation, logging, queues, tests).
Update and complete JournalOS translation JSON files by running composer journalos:locale and fixing missing or empty translations in lang/*.json. Use when UI copy changes, new keys are added, or locale files a...
Update the README.md file to list all available journal modules under the Features section with categorized, collapsible sections. Use when adding, removing, or reorganizing modules and keeping documentation in...
Guide for proving confluence of a rewriting system. Use when asked to prove Church-Rosser or confluence properties.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.