ThaddeusJiang

Unified Vmemo local development workflow: setup-state check, reset decision, and temporary port conflict handling.

Run the full GitHub PR lifecycle: create, update, assign, and keep PR content in sync with new commits.

Prepare a Vmemo release PR with explicit config-change confirmation gates.

Create concise incident postmortems at others/postmortem/YYYY-MM-DD-title.md for non-trivial bugs or issues.

开发时必须遵守 Vmemo 的编码规范与工程约束。

Use when working on Phoenix projects with Tidewave MCP. Prefer Tidewave tools for code discovery, docs lookup, runtime checks, and database verification instead of ad-hoc guessing.

Use this skill when publishing or updating the Vmemo Zeabur template, including pre-publish validation, manual Zeabur console steps, and post-publish link updates.

Vmemo Playwright e2e: author scoped specs, run in UI mode when possible, enforce local Docker + Phoenix prerequisites, and iterate fix-test until requirements pass.

Use git-cz or Commitizen to create semantic git commits and configure repositories for guided commit message generation. Use when the user asks to run `git cz`, `git-cz`, set up Commitizen, customize changelog.config.js, or produce non-interactive conventional commits.

Enforce secure and reproducible GitHub Actions workflows by pinning every action to an immutable commit SHA with an explicit version comment.

Docker and Docker Compose best practices for reliable local/dev deployments and multi-arch image publishing. Use when writing or reviewing Dockerfiles, Compose files, or CI publish workflows.

Elixir and Phoenix best practices for interactive development, debugging, testing, and routine code changes. Use when writing, reviewing, or troubleshooting Elixir application code, Mix tasks, Ecto code, or Phoenix features.

Create, update, and review Architecture Decision Records using the MADR minimal template.

Prepare any git worktree by copying shared files from the main checkout using git common-dir metadata.

Maintain CHANGELOG entries following Keep a Changelog 1.1.0 with project-aligned versioning. Use when creating, updating, or reviewing changelog content for releases.

Frontend coding conventions and review checklist for React/TypeScript projects. Use when implementing, reviewing, or refactoring frontend code to enforce project standards.

Use when working on `save_it` local development, setup, dev server startup, local checks, Typesense migrations, or code submission workflow.

Use Docker Compose to build and run the acceptance environment for `save_it`.

Prepare, verify, and publish `save_it` releases by updating `mix.exs`, creating the release commit and tag, and publishing a GitHub release. Use when the user asks to cut a stable release, prepare a prerelease, or verify release readiness for this repository. This repository uses CalVer `YYYY.M.D` for stable releases and prerelease tags such as `YYYY.M.D-rc.N`.

Maintain the save_it repository CHANGELOG.md using Keep a Changelog 1.1.0 with CalVer version headings. Use at the end of repository work, before final response or commit/PR handoff, when user-facing product behavior, features, fixes, removals, security changes, or breaking changes changed.

Generic response behavior policy for skill-capable AI agents. Use when an agent needs reusable rules for when to reply, when to stay silent, when to clarify ambiguous intent, and how to respect host permissions and routing across channels like Telegram, Slack, Discord, or CLI.

GitHub CLI operations for issues and pull requests. Use when creating, reading, updating, or closing issues and PRs. Always verify operations after execution.

Build or modify UI based on Figma designs by using the official Figma remote MCP server to inspect frames, styles, and components, then generate code that matches the project's styling system (SCSS or Tailwind CSS). Use when the user asks to implement UI from Figma or update UI to match a Figma file/node.

Persistent memory management using nmem CLI. Use when the user asks to remember, log, store, search, update, or delete memory. Execution via nmem CLI is mandatory; never simulate persistence.

Create, validate, update, and maintain Zeabur templates using official Template Resource YAML format and maintainer best practices.