twinfo-io
- 13 skills
- 0 followers
- 10 hours ago last updated
- ▌ Lf Exec · twinfo-io bundleStarts the execution of a specific work package (WP-XX) from a generated wps.md. Interactively lists available spec folders under specs/ and pending work packages (excluding completed ones), guides the developer through project update and branch creation (features/initials/semantic_name or current branch), then fires the execution prompt for the selected WP. No arguments required.
- ▌ Lf Push · twinfo-ioPushes the current branch and creates or updates a PR against the project's base/staging branch (auto-detected, overridable), filling the body from the repo's PR template if present — falling back to a minimal template otherwise — with type/ticket already resolved, and automatically comments the PR link on the linked issue-tracker ticket (Linear or GitHub Issues) once the PR is created. Always confirms before pushing or creating/updating the PR. Use when the user asks to push the branch, open a PR, or says something like 'push this'/'abre o PR'. If there are uncommitted changes, suggests /lf-commit first.
- ▌ Lf Specs · twinfo-io bundleGenerates specs.md and wps.md after the UX/UI team delivers Figma screens. Reads the latest briefing-tech.vN.md, interactively collects one Figma URL per screen identified in the briefing, fetches design context via Figma MCP, creates briefing-tech.v(N+1).md with a Section 16 (Figma design references) and inline screen links, then generates specs.md (SPEC-XX per domain with 12 sections each and Figma URLs inline) and wps.md (work packages with dependency map). Run after /lf-new-feature once the UX/UI team has shared Figma screen URLs. Accepts optional feature folder name as argument.
- ▌ Lf Commit · twinfo-ioBuilds and creates a commit following conventional-commit style: type (feat/fix) resolved from the current branch prefix, ticket ID resolved from the branch name or from the project's issue tracker (Linear or GitHub Issues — detected from project docs or asked once per project), English subject and Portuguese body. Always presents the draft and only commits after explicit confirmation. Use when the user asks to commit, generate/review the commit message, or says something like 'commit this'/'cria o commit'. Suggests running /lf-push afterward.
- ▌ Lf Git Push · twinfo-ioPushes commits safely in the correct order: submodules first, then the main repo. Checks which repos have unpushed commits, shows a push plan with the commit list per repo, confirms before executing, and stops immediately on failure to avoid broken references in the remote. Use instead of pushing manually to prevent 'submodule not pushed' errors on the main repo.
- ▌ Lf Git Sync · twinfo-ioPulls and synchronizes all git submodules with their remotes. Detects the git root, lists all submodules, pulls the main repo, then for each submodule: pulls if on a tracked branch or runs git submodule update if in detached HEAD state. Handles merge conflicts, network errors, and missing remotes gracefully. Shows a before/after summary with branch and commit state per repo. Use when you need to sync a monorepo with submodules after a teammate pushed changes.
- ▌ Lf Discovery · twinfo-io bundleInteractive feature discovery for product development teams. Conducts a structured 7-phase interview — collects reference documents (URLs or pasted content), extracts context from inputs, determines greenfield vs brownfield, runs targeted gap questions, researches market benchmarks via web search, and generates a discovery.md artifact. Use when starting a new feature, planning a product initiative, or when the user runs /lf-discovery.
- ▌ Lf Git Branch · twinfo-ioCreates a new git branch across the main repo and selected submodules. Accepts the branch name as argument or asks interactively. Lists all submodules and lets the user select all or specific ones. Creates from current HEAD or a specified base ref. Optionally pushes to remote. Shows a confirmation plan before executing. Use when starting a new feature that spans multiple submodules.
- ▌ Lf Git Status · twinfo-ioConsolidated git status view across the main repo and all submodules. Shows branch, ahead/behind remote, and dirty/clean state for every repo in a single scannable report. Flags issues: detached HEAD, local-only commits, diverged branches, and pointer mismatches between main repo and submodules. Use instead of running git status in each submodule manually.
- ▌ Lf Briefing UX · twinfo-io bundleGenerates the UX/UI briefing from an existing discovery.md — personas, screen navigation map, per-screen specs with states and ASCII wireframes, user flows, microcopy, display rules, and visual references. Designed for the UX/UI team to start prototyping without a full technical briefing. Use after /lf-discovery and before /lf-new-feature. Produces briefings/briefing-ux.v0.md (or vN if iterating).
- ▌ Lf New Feature · twinfo-io bundleGenerates the technical briefing (briefing-tech.vN.md, 15 sections) from an existing discovery.md. Can be called multiple times to iterate versions (v0 → v1 → v2). If briefing-ux.vN.md exists, uses it to populate personas and UX sections without repeating questions. Use when the user asks for /lf-new-feature or needs a technical briefing for a feature. Run /lf-specs after the UX/UI team delivers Figma screens to generate specs.md and wps.md.
- ▌ Lf Git Checkout · twinfo-ioSwitches branches across the main repo and all submodules. Accepts the branch name as argument or lists available branches interactively. Shows which submodules have the target branch vs which will be aligned via git submodule update. Detects uncommitted changes and offers stash per submodule. Confirms before executing. Use when switching feature branches in a monorepo with submodules.
- ▌ Lf Design System · twinfo-io bundleConnects to Figma via MCP Server, extracts typography, colors, spacing, border radius, shadows and all design token definitions, and generates specs/design-system.md — the official design system source of truth for the project. Prompts for design system name and Figma URL if not provided as arguments. Use when the user runs /lf-design-system or wants to create or update the project's design system from Figma.