hieutrtr
- 32 skills
- 0 followers
- 8 repo stars
- 2 months ago last updated
- ▌ News Impact · hieutrtrPhân tích tác động tin tức lên cổ phiếu Việt Nam — sentiment, catalyst, rủi ro sự kiện. Dùng khi user hỏi về tin tức, news, sự kiện sắp tới, catalyst, hoặc sentiment của một mã cụ thể.
- ▌ News Update · hieutrtrThu thập tin tức mới từ CafeF/Vietstock/VNExpress, deduplicate với archive, chỉ hiển thị tin chưa từng thấy. Dùng khi user muốn cập nhật tin tức mới nhất mà không bị lặp lại tin cũ.
- ▌ Morning Brief · hieutrtrPre-market morning brief — market overview, portfolio status, overnight news. Use before trading session starts.
- ▌ Sector Compare · hieutrtrSo sánh ngành và vị thế tương đối của cổ phiếu Việt Nam trong cùng sector — peer analysis. Dùng khi user muốn so sánh các cổ phiếu cùng ngành, peer analysis, hoặc tìm cổ phiếu tốt nhất trong một sector.
- ▌ Stock Screener · hieutrtrLọc cổ phiếu Việt Nam theo tiêu chí tài chính, kỹ thuật, hoặc kết hợp — tìm cơ hội đầu tư. Dùng khi user muốn lọc/tìm cổ phiếu, chạy screener, scan cơ hội, hoặc tìm mã theo điều kiện cụ thể.
- ▌ Session Summary · hieutrtrEnd-of-day trading session summary — P&L, market recap, top movers, news highlights, action items for tomorrow.
- ▌ Watchlist Check · hieutrtrCheck watchlist conditions from data/watchlist.json and alert when triggered. Designed for /loop 5m usage.
- ▌ Portfolio Review · hieutrtrĐánh giá danh mục đầu tư Việt Nam — hiệu suất, rủi ro, phân bổ, và khuyến nghị tái cơ cấu. Dùng khi user muốn review/đánh giá danh mục, phân bổ tài sản, hoặc tái cơ cấu portfolio.
- ▌ Portfolio Monitor · hieutrtrMonitor portfolio positions for price changes, volume spikes, and ceiling/floor alerts. Designed for /loop 5m usage during trading sessions.
- ▌ Technical Analysis · hieutrtrPhân tích kỹ thuật một mã cổ phiếu Việt Nam — xu hướng, momentum, tín hiệu mua/bán. Dùng khi user hỏi về chart, RSI, MACD, support/resistance, hỗ trợ, kháng cự, hoặc tín hiệu mua/bán kỹ thuật.
- ▌ Fundamental Analysis · hieutrtrPhân tích cơ bản một mã cổ phiếu Việt Nam — định giá, tài chính, triển vọng ngành. Dùng khi user hỏi về P/E, P/B, ROE, EPS, định giá, BCTC, báo cáo tài chính, hoặc phân tích cơ bản (FA).
- ▌ Auto Test · hieutrtr bundleRun a project's automated tests end-to-end and return a single structured report (ASCII dashboard + machine-readable trailing lines + path to .test-runs/<UTC-ts>/run.log). Trigger when the user asks to run, execute, or check the status of a project's tests — phrases like "run the unit tests", "run the tests", "execute the test suite", "ai check tests for me", "run npm test and tell me what failed", or "how are the tests doing?". This is the meta-skill that delegates to layer-specific runners (Phase 1 ships only the `unit-test-runner` child); future phases will add `browser-test`, `integration-test-runner`, and `coverage-reporter` to the same orchestration. Do NOT trigger on "tail the log", "show me the latest test output", or "what does .test-runs/latest contain?" — those are plain `Read` of `<project>/.test-runs/latest/run.log`. Do NOT trigger on lint, typecheck, build, deploy, or coverage-only requests — those belong to other (separate) skills. Do NOT trigger on browser-only / Playwright-with-page.goto navi
- ▌ Unit Test Runner · hieutrtr bundleDetect the JavaScript / TypeScript unit-test framework in a project (Jest, Vitest, bun:test, Mocha, or @playwright/test used as a unit-test runner) and prepare a canonical run command. Trigger when another testing skill — usually `auto-test` — needs to know "what unit-test framework does this repo use, what command should I run, and which JS runtime / package manager (npm, pnpm, yarn, bun) drives it?". Concretely fires on user phrases like "run the unit tests", "what framework do these tests use?", "detect the test runner for this project", or as a sub-step of `auto-test`. Do NOT trigger on "run end-to-end tests" / "browser tests" / "integration tests" / "Playwright e2e tests with a dev server" — those belong to the Phase 2 `browser-test` skill (this skill's `playwright-runner` framework keyword is reserved for `@playwright/test` used WITHOUT browser navigation, i.e. as a generic test runner). Do NOT trigger on Python (pytest), Rust (cargo test), Go (`go test`), Ruby (rspec), or Elixir tests — those are Phase
- ▌ Test Log Centralizer · hieutrtr bundleCentralize test-run logs under <project>/.test-runs/<UTC-timestamp>/ so every other testing skill (auto-test, unit-test-runner, browser-test, integration-test-runner, flaky-detector, coverage-reporter) writes into a single shared run folder. Use ONLY as a dependency invoked by another testing skill — it is not user-facing on its own. Trigger when another skill needs to (a) start a new run folder via `scripts/init-run.sh`, (b) append per-layer log lines via `scripts/append-log.sh`, or (c) finalize a run via `scripts/finalize-run.sh`. Do NOT trigger on user phrases like "show me the logs", "tail the logs", "check what tests printed" — those should call `auto-test` (which internally uses this skill) or read `<project>/.test-runs/latest/run.log` directly with the Read tool. Do NOT use this skill for non-test logging (application logs, build output, lint output) — those belong to other tools.
- ▌ Hello Test · hieutrtrPhase-0 spike probe used to verify Claude Code skill discovery and triggering. Trigger ONLY when the user message contains the literal phrase "hello-test ping" — no paraphrases, no partial matches. Output is a single fixed acknowledgement string with the current ISO-8601 UTC timestamp, produced by running a one-liner Bash command. Do NOT trigger on the words "hello", "test", "ping" individually, on phrases like "hello world", "say hello", "ping me", or any other variant. This skill exists purely as a fingerprint for the auto-test-skills repo Phase 0 spike to confirm that user-level skills dropped at ~/.claude/skills/<name>/SKILL.md are auto-discovered. Safe to delete after Phase 0 sign-off.
- ▌ Tdd Workflow · hieutrtrTest-driven development workflow enforcement for Python and React projects. Use when the user requests TDD, test-first development, or red-green-refactor methodology. Enforces strict cycle: write ONE failing test -> implement minimum code to pass -> refactor while green -> repeat. Applies to both backend (pytest) and frontend (Testing Library). Changes agent behavior to write tests before code. Does NOT provide testing patterns (use pytest-patterns or react-testing-patterns for how to write tests).
- ▌ Project Planner · hieutrtr bundleProject planning and feature breakdown for Python/React full-stack projects. Use during the planning phase when breaking down feature requests, user stories, or product requirements into implementation plans. Guides identification of affected files and modules, defines acceptance criteria, assesses risks, and estimates overall complexity. Produces module maps, risk assessments, and acceptance criteria. Does NOT cover architecture decisions (use system-architecture), implementation (use python-backend-expert or react-frontend-expert), or atomic task decomposition (use task-decomposition).
- ▌ Pytest Patterns · hieutrtr bundlePython backend testing patterns with pytest for FastAPI applications. Use when writing Python tests: unit tests for services and repositories, integration tests for API endpoints with httpx.AsyncClient, fixture creation, factory setup with factory_boy, async testing with pytest-asyncio, mocking strategies, and parametrized tests. Covers test organization (tests/unit, tests/integration), conftest hierarchy, and coverage requirements. Does NOT cover frontend tests (use react-testing-patterns) or E2E browser tests (use e2e-testing).
- ▌ Fastapi Patterns · hieutrtr bundleFastAPI framework mechanics and advanced patterns. Use when configuring middleware, creating dependency injection chains, implementing WebSocket endpoints, customizing OpenAPI documentation, setting up CORS, building authentication dependencies (JWT validation, role-based access), implementing background tasks, or managing application lifespan (startup/shutdown). Does NOT cover basic endpoint CRUD or repository/service patterns (use python-backend-expert) or testing (use pytest-patterns).
- ▌ Monitoring Setup · hieutrtr bundleApplication monitoring and observability setup for Python/React projects. Use when configuring logging, metrics collection, health checks, alerting rules, or dashboard creation. Covers structured logging with structlog, Prometheus metrics for FastAPI, health check endpoints, alert threshold design, Grafana dashboard patterns, error tracking with Sentry, and uptime monitoring. Does NOT cover incident response procedures (use incident-response) or deployment (use deployment-pipeline).
- ▌ UI Design System · hieutrtr bundleGenerates consistent UI components, layouts, and design tokens following a design system. Enforces spacing, color, typography, and accessibility standards across React/TypeScript projects. Use when creating new UI components, building page layouts, choosing colors or typography, setting up design tokens, or reviewing UI code for design consistency. Covers 8pt spacing grid, Tailwind CSS token usage, shadcn/ui primitives, WCAG 2.1 AA compliance, responsive breakpoints, semantic HTML structure, and TypeScript component interfaces. Does NOT cover backend implementation (use python-backend-expert), testing (use react-testing-patterns), or deployment (use deployment-pipeline).
- ▌ Incident Response · hieutrtr bundleProduction incident response procedures for Python/React applications. Use when responding to production outages, investigating error spikes, diagnosing performance degradation, or conducting post-mortems. Covers severity classification (SEV1-SEV4), incident commander role, communication templates, diagnostic commands for FastAPI/ PostgreSQL/Redis, rollback procedures, and blameless post-mortem process. Does NOT cover monitoring setup (use monitoring-setup) or deployment procedures (use deployment-pipeline).
- ▌ Task Decomposition · hieutrtr bundleDecompose high-level objectives into atomic implementation tasks for Python/React projects. Use when breaking down large features, multi-file changes, or tasks requiring more than 3 steps. Produces independently-verifiable tasks with done-conditions, file paths, complexity estimates, and explicit ordering. Creates persistent task files (task_plan.md, progress.md) to track state across context windows. Does NOT cover high-level planning (use project-planner) or architecture decisions (use system-architecture).
- ▌ API Design Patterns · hieutrtr bundleAPI contract design conventions for FastAPI projects with Pydantic v2. Use during the design phase when planning new API endpoints, defining request/response contracts, designing pagination or filtering, standardizing error responses, or planning API versioning. Covers RESTful naming, HTTP method semantics, Pydantic v2 schema naming conventions (XxxCreate/XxxUpdate/XxxResponse), cursor-based pagination, standard error format, and OpenAPI documentation. Does NOT cover implementation details (use python-backend-expert) or system-level architecture (use system-architecture).
- ▌ Deployment Pipeline · hieutrtr bundleDeployment procedures and CI/CD pipeline configuration for Python/React projects. Use when deploying to staging or production, creating CI/CD pipelines with GitHub Actions, troubleshooting deployment failures, or planning rollbacks. Covers pipeline stages (build/test/staging/production), environment promotion, pre-deployment validation, health checks, canary deployment, rollback procedures, and GitHub Actions workflows. Does NOT cover Docker image building (use docker-best-practices) or incident response (use incident-response).
- ▌ Pre Merge Checklist · hieutrtr bundleComprehensive pre-merge validation checklist for Python/React pull requests. Use before approving or merging any PR. Covers code quality checks (linting, formatting, type checking), test coverage requirements, documentation updates, migration safety, API contract compatibility, accessibility compliance, bundle size impact, and deployment readiness. Provides a systematic checklist that ensures nothing is missed before merge. Does NOT cover security review depth (use code-review-security).
- ▌ System Architecture · hieutrtr bundleSystem architecture guidance for Python/React full-stack projects. Use during the design phase when making architectural decisions — component boundaries, service layer design, data flow patterns, database schema planning, and technology trade-off analysis. Covers FastAPI layer architecture (Routes/Services/Repositories/Models), React component hierarchy, state management, and cross-cutting concerns (auth, errors, logging). Produces architecture documents and ADRs. Does NOT cover implementation (use python-backend-expert or react-frontend-expert) or API contract design (use api-design-patterns).
- ▌ Code Review Security · hieutrtr bundleSecurity-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention, XSS protection, CSRF tokens, authentication flow review, secrets detection, dependency vulnerability scanning, and secure coding patterns for Python (FastAPI) and React. Does NOT cover deployment security (use docker-best-practices) or incident handling (use incident-response).
- ▌ Docker Best Practices · hieutrtr bundleDocker containerization patterns for Python/React projects. Use when creating or modifying Dockerfiles, optimizing image size, setting up Docker Compose for local development, or hardening container security. Covers multi-stage builds for Python (python:3.12-slim) and React (node:20-alpine -> nginx:alpine), layer optimization, .dockerignore, non-root user, security scanning with Trivy, Docker Compose for dev (backend + frontend + PostgreSQL + Redis), and image tagging strategy. Does NOT cover deployment orchestration (use deployment-pipeline).
- ▌ Python Backend Expert · hieutrtr bundlePython backend implementation patterns for FastAPI applications with SQLAlchemy 2.0, Pydantic v2, and async patterns. Use during the implementation phase when creating or modifying FastAPI endpoints, Pydantic models, SQLAlchemy models, service layers, or repository classes. Covers async session management, dependency injection via Depends(), layered error handling, and Alembic migrations. Does NOT cover testing (use pytest-patterns), deployment (use deployment-pipeline), or FastAPI framework mechanics like middleware and WebSockets (use fastapi-patterns).
- ▌ React Frontend Expert · hieutrtr bundleReact/TypeScript frontend implementation patterns. Use during the implementation phase when creating or modifying React components, custom hooks, pages, data fetching logic with TanStack Query, forms, or routing. Covers component structure, hooks rules, custom hook design (useAuth, useDebounce, usePagination), TypeScript strict-mode conventions, form handling, accessibility requirements, and project structure. Does NOT cover testing (use react-testing-patterns), E2E testing (use e2e-testing), or deployment.
- ▌ React Testing Patterns · hieutrtr bundleReact component and hook testing patterns with Testing Library and Vitest. Use when writing tests for React components, custom hooks, or data fetching logic. Covers component rendering tests, user interaction simulation, async state testing, MSW for API mocking, hook testing with renderHook, accessibility assertions, and snapshot testing guidelines. Does NOT cover E2E tests (use e2e-testing) or TDD workflow enforcement (use tdd-workflow).