fynt-workflow-platform-core
SKILL.md
Fynt Workflow Platform Core
Use this skill for Phase 2 quality work: post-auth product UX plus execution backend correctness.
Invocation Contract
$fynt-workflow-platform-core mode=clone$fynt-workflow-platform-core mode=adapt$fynt-workflow-platform-core mode=upgrade
If mode is missing, default to adapt.
Mode Behavior
clone: stay closest to Fynt product DNA (dark shell, orange accents, dense-but-readable cards, React Flow editor behavior, queue+socket runtime model).adapt: preserve architecture and reliability patterns while retheming and renaming for another brand/product.upgrade: transform an existing authenticated app and backend to this quality bar with explicit before/after improvements.
Required Output Contract
Always include all items before finalizing:
- Product information architecture and section/page map.
- Frontend interaction plan (dashboard states, editor behavior, list/detail flows, responsive behavior).
- Motion and feedback plan (entry/hover/loading/state transitions + reduced-motion path).
- Backend contract plan (query/mutation schemas, limits, validation, ownership checks).
- Execution lifecycle plan (UI -> API -> queue -> worker -> redis pub/sub -> websocket client fallback).
- Security and reliability plan (credentials, rate limits, locks, retries, rollback strategy).
- Accessibility and performance checks.
- Rubric scorecard with pass/fail.
Do not finalize without a pass from references/quality-rubric.md.
Workflow
- Identify mode and whether scope is
greenfieldorexisting code upgrade. - Read references/source-pattern-map.md first.
- Load only needed references:
- Reuse starter scaffolds when code is requested:
- Perform strict rubric scoring and iterate until pass.
Non-Negotiables
- Keep runtime-mode gating explicit (
fullvsweb-only) for execution paths. - Enforce graph validation and template graph integrity before persistence.
- Guard executions with ownership checks, plan limits, and concurrency limits.
- Keep reduced-motion support in authenticated UX, not only marketing pages.
- Provide fallback behavior for realtime status (socket disconnect -> polling).
- Keep credential handling encrypted and never expose raw secrets in UI payloads.
Anti-Patterns To Reject
- Pretty dashboard with no execution correctness contract.
- Generic CRUD editor without graph validation, autosave safeguards, or undo/redo.
- Webhook endpoints without secret verification, rate limits, or plan reservation checks.
- Realtime status flows that fail silently on socket drops.
- Platform outputs that ignore mobile behavior, loading states, or empty/error states.
Framework Baseline
Default target stack is Next.js + Tailwind CSS + Framer Motion + React Flow + tRPC + BullMQ + Redis + WebSocket.
Weekly Installs
1
Repository
bhaktofmahakal/…t-skillsFirst Seen
9 days ago
Security Audits
Installed on
amp1
cline1
opencode1
cursor1
kimi-cli1
codex1