tuanloc1105
- 46 skills
- 0 followers
- 11 hours ago last updated
- ▌ Plan · tuanloc1105 bundlePlan-first collaboration workflow for Codex. Creates one dated, daily-sequenced version 4 Markdown plan bundle under ./plans/, keeps it active through approval and execute handoff, and stores every declared phase in its own self-contained, stable-ID Markdown file under phases/. Use for reviewed implementation planning and durable cross-session handoff.
- ▌ Discuss · tuanloc1105 bundleUse when the user invokes $discuss or requests discussion work with a persistent version 4 Markdown record bundle. Start a new dated, daily-sequenced bundle by default, even when an older bundle is supplied; reuse an older bundle only when the user explicitly asks to continue it. Keep discuss active across scoped actions and exit only through $plan or $execute.
- ▌ Execute · tuanloc1105 bundlePersistent execution and evidence-tracking mode for an approved version 4 Markdown record bundle produced by $plan or execution-ready $discuss. Keep the exact bundle active, execute dependency-ready phase files, update evidence and verification transactionally, and remain active until explicit exit.
- ▌ Simplify · tuanloc1105 bundleSimplify recently changed code while preserving behavior. Use when the user asks to simplify, clean up, refactor, deduplicate, reduce state or indirection, improve reuse, or make frontend, backend, shared, infrastructure, or test code clearer and smaller in conceptual surface.
- ▌ Data Debug · tuanloc1105 bundleSafely inspect and troubleshoot Oracle, PostgreSQL, MySQL, MongoDB, Redis, or Microsoft SQL Server through the db-debug:latest Docker image. Use for database connectivity checks, metadata inspection, read-only queries, query-plan analysis, or database incident debugging. All database work is read-only by default; mutations require explicit approval for the exact operation.
- ▌ Split Code · tuanloc1105 bundleSplit oversized files, functions, methods, classes, modules, or packages into smaller readable units without changing behavior. Use when the user asks to split code, tách code, break up a long function/file, extract helpers, modularize code, move logic into modules/packages, or make code easier to read while preserving the exact existing logic, inputs, outputs, side effects, errors, ordering, and public API compatibility.
- ▌ Code Review · tuanloc1105 bundleClaude-Code-inspired code review workflow for diffs, pull requests, branches, commits, or working-tree changes. Use for minimal, low, low-minimum/low-expanded, medium, high, extra-high/xhigh, or max/maximum-effort reviews; precision- or recall-biased bug finding; language/framework pitfalls; wrapper, proxy, decorator, or adapter correctness; three-state verification; raw JSON or typed ReportFindings output; GitHub inline comments; opt-in review artifacts; applying verified fixes with --fix; or explaining Claude-only ultra/ultrareview behavior.
- ▌ Plan 2 · tuanloc1105 bundlePlan-first collaboration workflow for Antigravity. Creates one dated, daily-sequenced version 4 Markdown plan bundle under ./plans/, keeps it active through approval and execute handoff, and stores every declared phase in its own self-contained, stable-ID Markdown file under phases/. Use for reviewed implementation planning and durable cross-session handoff.
- ▌ Anti AI Design · tuanloc1105 bundleAuto-orchestrating UI design skill that prevents generic AI-generated output. Detects project context and target platform, explicitly asks the user which platforms to design for, resolves brand color direction through user choice or auto-selection, presents curated design style options, and generates a CJX-ready output bundle with html/css/js folders plus frozen foundation tokens for visual consistency. Use when asked for: UI design, landing pages, dashboards, app screens, product pages, onboarding flows, or any visual interface output. Enforces 18 banned patterns and 12 required quality signals inline on every generation.
- ▌ Handoff Execute · tuanloc1105 bundleCoordinate execution of an approved version 4 $plan bundle or execution-ready $discuss tracker by launching a separate lower-cost Codex CLI session, then reconcile its work, run $simplify in the current session, and complete verification. Use when the user explicitly requests $handoff-execute or asks to hand off an accepted execution record to another Codex CLI session. Never use subagents for this workflow.
- ▌ Kiro Plan · tuanloc1105 bundlePlan-first collaboration workflow for Kiro / Kiro Crew. Creates one dated, daily-sequenced version 4 Markdown plan bundle under ./plans/, keeps it active through approval and execute handoff, and stores every declared phase in its own self-contained, stable-ID Markdown file under phases/. Use for reviewed implementation planning and durable cross-session handoff. Kiro port of the Codex `plan` skill.
- ▌ Security Review · tuanloc1105 bundleAttacker-minded, multi-agent application security review for repositories, pull requests, diffs, APIs, backend/frontend code, infrastructure/config files, CI/CD, cloud/container/IaC, AI/LLM features, and dependency manifests. Use when Codex is asked to scan or review code for OWASP Top 10 risks, authentication bypass, broken access control, IDOR/BOLA, injection, XSS, CSRF, SSRF, security misconfiguration, sensitive data exposure, dependency vulnerabilities, business logic abuse, file handling/path traversal, deserialization, race conditions, DoS/resource exhaustion, supply chain issues, API security, session/token/cookie hardening, monitoring/incident readiness, or hardening topics such as input validation, output encoding, rate limiting, secret management, encryption, logging/audit trails, least privilege, and network segmentation.
- ▌ Surgical Coding · tuanloc1105Use for non-trivial code edits, bug fixes, refactors, tests, reviews, and repo-grounded implementation. Emphasizes reading before writing, surgical scope, local conventions, and narrow verification.
- ▌ Discuss 2 · tuanloc1105 bundleUse when the user invokes $discuss, /discuss, or requests discussion work with a persistent version 4 Markdown record bundle. Start a new dated, daily-sequenced bundle by default, even when an older bundle is supplied; reuse an older bundle only when the user explicitly asks to continue it. Keep discuss active across scoped actions and exit only through plan or execute.
- ▌ Execute 2 · tuanloc1105 bundlePersistent execution and evidence-tracking mode for an approved version 4 Markdown record bundle produced by plan or execution-ready discuss. Keep the exact bundle active, execute dependency-ready phase files, update evidence and verification transactionally, and remain active until explicit exit.
- ▌ Plan 3 · tuanloc1105 bundlePlan-first collaboration workflow for Claude Code. Creates one dated, daily-sequenced version 4 Markdown plan bundle under ./plans/, keeps it active through approval and execute handoff, and stores every declared phase in its own self-contained, stable-ID Markdown file under phases/. Use for reviewed implementation planning and durable cross-session handoff.
- ▌ Mermaid Flowchart · tuanloc1105 bundleCreate or edit a technical workflow/flowchart from session context, natural-language processes, code paths, or Mermaid flowchart source. This is the permanent flowchart-only compatibility alias for technical-diagrams; do not use it for sequence, state, data-flow, or other diagram families.
- ▌ Update Agent Docs · tuanloc1105 bundleCreate, refresh, or repair repository agent documentation centered on AGENTS.md. Use when the user asks Codex to update AGENTS.md, create agent docs, document a codebase for future agent sessions, resolve AGENTS.md symlinks or @CLAUDE.md-style includes, migrate useful guidance from Claude/Cursor/Copilot/Devin/Windsurf/Cline/Gemini/Codex configs, generate docs/agent routing maps, run multi-agent project discovery, or prepare a commit/push prompt for agent-doc changes.
- ▌ Simplify 2 · tuanloc1105 bundleSimplify recently changed code while preserving behavior. Use when the user asks to simplify, clean up, refactor, deduplicate, reduce state or indirection, improve reuse, or make frontend, backend, shared, infrastructure, or test code clearer and smaller in conceptual surface.
- ▌ Deliver Ocb Change · tuanloc1105 bundleDeliver OCB Backend or web Frontend Developer work from Jira verification through approved planning, implementation, domain-specific verification, LinearB-visible Git delivery, and developer-performed GitLab merge. Use for explicit `$deliver-ocb-change` requests, OCB backend, frontend, or mixed Jira implementation or plan execution, OCB-traceable GitLab MR preparation, and verified merge. Do not use for generic coding advice, Mobile delivery, unrelated Jira administration, deployment, release, self-approval, or generic LinearB reporting.
- ▌ Interact With Jira · tuanloc1105 bundleWork with Jira Cloud through Atlassian Rovo MCP first, registered or dynamically verified official Jira REST fallbacks when MCP lacks a capability or is unavailable, and official Atlassian CLI `acli` only when explicitly requested or approved. Use for Jira reads, writes, attachments, boards, sprints, releases, configuration, authentication, and safety gates.
- ▌ Kiro Discuss · tuanloc1105 bundleUse when the user invokes $discuss or requests discussion work with a persistent version 4 Markdown record bundle. Start a new dated, daily-sequenced bundle by default, even when an older bundle is supplied; reuse an older bundle only when the user explicitly asks to continue it. Keep discuss active across scoped actions and exit only through $plan or $execute. Kiro / Kiro Crew port of the Codex `discuss` skill.
- ▌ Kiro Execute · tuanloc1105 bundlePersistent execution and evidence-tracking mode for an approved version 4 Markdown record bundle produced by $plan or execution-ready $discuss. Keep the exact bundle active, execute dependency-ready phase files, update evidence and verification transactionally, and remain active until explicit exit. Kiro port of the Codex `execute` skill.
- ▌ Technical Diagrams · tuanloc1105 bundleCreate polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
- ▌ Windows Powershell · tuanloc1105 bundleReliable Windows PowerShell 5.1 and PowerShell 7+ command authoring, execution, troubleshooting, and Bash-to-PowerShell translation for Codex on Windows. Use when working in Windows terminals, `powershell.exe`, `pwsh`, PowerShell scripts (`.ps1`, `.psm1`, `.psd1`), Windows paths, native `.exe`/`.bat`/`.cmd` commands, Windows CI jobs, or when a user reports command failures caused by shell syntax, quoting, paths, aliases, redirection, execution policy, native argument passing, or exit-code handling.
- ▌ Kiro Simplify · tuanloc1105 bundleSimplify recently changed code while preserving behavior. Use when the user asks to simplify, clean up, refactor, deduplicate, reduce state or indirection, improve reuse, or make frontend, backend, shared, infrastructure, or test code clearer and smaller in conceptual surface. Kiro port of the Codex `simplify` skill.
- ▌ Discuss 3 · tuanloc1105 bundleUse when the user invokes /discuss or requests discussion work with a persistent version 4 Markdown record bundle. Start a new dated, daily-sequenced bundle by default, even when an older bundle is supplied; reuse an older bundle only when the user explicitly asks to continue it. Keep discuss active across scoped actions and exit only through /plan or /execute.
- ▌ Execute 3 · tuanloc1105 bundlePersistent execution and evidence-tracking mode for an approved version 4 Markdown record bundle produced by /plan or execution-ready /discuss. Keep the exact bundle active, execute dependency-ready phase files, update evidence and verification transactionally, and remain active until explicit exit.
- ▌ Simplify 3 · tuanloc1105 bundleSimplify recently changed code while preserving behavior. Use when the user asks to simplify, clean up, refactor, deduplicate, reduce state or indirection, improve reuse, or make frontend, backend, shared, infrastructure, or test code clearer and smaller in conceptual surface.
- ▌ Kiro Data Debug · tuanloc1105 bundleSafely inspect and troubleshoot Oracle, PostgreSQL, MySQL, MongoDB, Redis, or Microsoft SQL Server through the db-debug:latest Docker image. Use for database connectivity checks, metadata inspection, read-only queries, query-plan analysis, or database incident debugging. All database work is read-only by default; mutations require explicit approval for the exact operation. Kiro port of the Codex `data-debug` skill.
- ▌ Data Debug 2 · tuanloc1105 bundleSafely inspect and troubleshoot Oracle, PostgreSQL, MySQL, MongoDB, Redis, or Microsoft SQL Server through the db-debug:latest Docker image. Use for database connectivity checks, metadata inspection, read-only queries, query-plan analysis, or database incident debugging. All database work is read-only by default; mutations require explicit approval for the exact operation.
- ▌ Kiro Codex Review · tuanloc1105 bundleLaunch an independent Codex CLI session to review findings in one exact workflow-record version 4 bundle produced by kiro-discuss, kiro-plan, or kiro-execute. Codex writes a durable review tracker into the bundle under a bounded ownership transfer; Kiro then validates and adjudicates it. Use when the user asks Kiro to obtain and track a Codex second opinion. Do not use for implementation handoff or ordinary Kiro subagent review.
- ▌ Teach For Understanding · tuanloc1105 bundleIncremental teaching and comprehension verification workflow for Codex sessions. Use when the user asks Codex to act as a wise/effective teacher, make sure they deeply understand a session, explain code or changes step by step, maintain a learning checklist, quiz the user, require restatement before moving on, or keep a goal active until the user demonstrates mastery of the problem, solution, edge cases, design decisions, and broader impact.
- ▌ Interact With Git Platform · tuanloc1105 bundleWork with GitHub, GitLab, and Gitea through their official command-line clients (`gh`, `glab`, and `tea`), including authentication, host and repository selection, issues, pull or merge requests, reviews, releases, CI, and API fallbacks. Use when Codex must inspect, configure, troubleshoot, or safely mutate a Git platform through these CLIs. Do not use for local-only `git` operations or unrelated hosting providers.
- ▌ Update Agent Docs 2 · tuanloc1105 bundleCreate, refresh, or repair repository agent documentation centered on AGENTS.md and GEMINI.md. Use when the user asks to update AGENTS.md/GEMINI.md, create agent docs, document a codebase for future agent sessions, resolve symlinks or includes, migrate useful guidance from other AI configs, generate docs/agent routing maps, run multi-agent project discovery, or prepare a commit/push prompt for agent-doc changes.
- ▌ Kiro Update Agent Docs · tuanloc1105 bundleCreate, refresh, or repair repository steering documentation centered on `.kiro/steering/*.md`. Use when the user asks Kiro to update steering docs, create agent-facing project docs, document a codebase for future Kiro sessions, migrate useful guidance from AGENTS.md/CLAUDE.md/Cursor/Copilot/Devin/Windsurf/Cline/Gemini configs, generate a docs/agent routing map, run multi-agent project discovery, or prepare a commit/push prompt for steering-doc changes. Kiro port of the Codex `update-agent-docs` skill.
- ▌ Kiro Deliver Ocb Change · tuanloc1105 bundleDeliver OCB Backend or web Frontend Developer work from Jira verification through approved planning, implementation, domain-specific verification, LinearB-visible Git delivery, and developer-performed GitLab merge. Use for explicit `$kiro-deliver-ocb-change` requests, OCB backend, frontend, or mixed Jira implementation or plan execution, OCB-traceable GitLab MR preparation, and verified merge. Do not use for generic coding advice, Mobile delivery, unrelated Jira administration, deployment, release, self-approval, or generic LinearB reporting. Kiro port of the Codex deliver-ocb-change skill.
- ▌ Kiro Interact With Jira · tuanloc1105 bundleWork with Jira Cloud through Atlassian Rovo MCP first, registered or dynamically verified official Jira REST fallbacks when MCP lacks a capability or is unavailable, and official Atlassian CLI `acli` only when explicitly requested or approved. Use for Jira reads, writes, attachments, boards, sprints, releases, configuration, authentication, and safety gates. Kiro port of the Codex interact-with-jira skill.
- ▌ Kiro Technical Diagrams · tuanloc1105 bundleCreate polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid. Kiro port of the Codex `technical-diagrams` skill.
- ▌ Update Agent Docs 3 · tuanloc1105 bundleCreate, refresh, or repair repository agent documentation centered on AGENTS.md. Use when the user asks Claude to update AGENTS.md, create agent docs, document a codebase for future agent sessions, resolve AGENTS.md symlinks or @CLAUDE.md-style includes, migrate useful guidance from Claude/Cursor/Copilot/Devin/Windsurf/Cline/Gemini/Codex configs, generate docs/agent routing maps, run multi-agent project discovery, or prepare a commit/push prompt for agent-doc changes.
- ▌ Deliver Ocb Change 2 · tuanloc1105 bundleDeliver OCB Backend or web Frontend Developer work from Jira verification through approved planning, implementation, domain-specific verification, LinearB-visible Git delivery, and developer-performed GitLab merge. Use for explicit `/deliver-ocb-change` requests, OCB backend, frontend, or mixed Jira implementation or plan execution, OCB-traceable GitLab MR preparation, and verified merge. Do not use for generic coding advice, Mobile delivery, unrelated Jira administration, deployment, release, self-approval, or generic LinearB reporting.
- ▌ Interact With Jira 2 · tuanloc1105 bundleWork with Jira Cloud through Atlassian Rovo MCP first, registered or dynamically verified official Jira REST fallbacks when MCP lacks a capability or is unavailable, and official Atlassian CLI `acli` only when explicitly requested or approved. Use for Jira reads, writes, attachments, boards, sprints, releases, configuration, authentication, and safety gates.
- ▌ Technical Diagrams 2 · tuanloc1105 bundleCreate polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
- ▌ Interact With Git Platform 2 · tuanloc1105 bundleWork with GitHub, GitLab, and Gitea through their official command-line clients (`gh`, `glab`, and `tea`), including authentication, host and repository selection, issues, pull or merge requests, reviews, releases, CI, and API fallbacks. Use when Antigravity must inspect, configure, troubleshoot, or safely mutate a Git platform through these CLIs. Do not use for local-only `git` operations or unrelated hosting providers.
- ▌ Kiro Interact With Git Platform · tuanloc1105 bundleWork with GitHub, GitLab, and Gitea through their official command-line clients (`gh`, `glab`, and `tea`), including authentication, host and repository selection, issues, pull or merge requests, reviews, releases, CI, and API fallbacks. Use when Kiro must inspect, configure, troubleshoot, or safely mutate a Git platform through these CLIs. Do not use for local-only `git` operations or unrelated hosting providers. Kiro port of the Codex `interact-with-git-platform` skill.
- ▌ Interact With Git Platform 3 · tuanloc1105 bundleWork with GitHub, GitLab, and Gitea through their official command-line clients (`gh`, `glab`, and `tea`), including authentication, host and repository selection, issues, pull or merge requests, reviews, releases, CI, and API fallbacks. Use when Claude must inspect, configure, troubleshoot, or safely mutate a Git platform through these CLIs. Do not use for local-only `git` operations or unrelated hosting providers.