fix(link): polished "What's next" block — numbered, colorized, single copy-paste command

[tonychang04]

Summary

After link --template, the CLI used to print two adjacent clack notes:

┌  Next steps  ───┐
│  cd my-app      │
│  npm run dev    │
└─────────────────┘
┌  Keep building  ──────────────────┐
│  Open your coding agent (Claude…) │
└───────────────────────────────────┘

Now it prints one block, numbered, with cd && npm run dev joined into a single copy-paste:

◇  What's next ──────────────────────────────────────────────────────────────╮
│                                                                            │
│  1. cd my-app && npm run dev                                               │
│  2. Open Claude Code or Cursor and prompt your agent to add more features  │
│                                                                            │
├────────────────────────────────────────────────────────────────────────────╯

Tokens are colorized via picocolors: cd / npm run dev / Claude Code / Cursor cyan, my-app green, && dim, dashboard URL underlined. (Colors don't show in this captured snippet.)

picocolors was already in the dep tree transitively via @clack/prompts; bumped to a direct dep since we now import it ourselves.

Test plan

• insforge link --project-id <id> --template todo from a real terminal — confirm the new combined "What's next" block renders with colors and step 1 is a single working copy-paste.
• Same command from Claude Code's bash — confirm output is still readable when ANSI codes get stripped.

🤖 Generated with Claude Code

Note

Polish the link command's "What's next" output with numbered steps and colors

Updates the post-link console output in src/commands/projects/link.ts using picocolors. The dashboard URL is now underlined, next steps are numbered and color-coded, and the separate "Keep building" note is removed. The combined run command is printed as a single copy-pasteable string.

^{Macroscope summarized f0a40db.}

Summary by CodeRabbit

• Improvements

  • Enhanced CLI output after template download: colorized, underlined links and a clearer, numbered "What's next" with a single highlighted command and explicit guidance to prompt your agent for more features.

• Chores

  • Version bumped to 0.1.48.
  • Added a runtime dependency for colorized terminal output.

[coderabbitai]

Walkthrough

Package version bumped to 0.1.48 and picocolors added as a new dependency. CLI output in the project link command was updated to use picocolors for colored and underlined next-step messaging and adjusted textual wording mentioning Claude Code and Cursor.

Changes

Cohort / File(s)	Summary
Package Configuration package.json	Version updated from 0.1.47 → 0.1.48; added runtime dependency picocolors ^1.1.1.
Command Output Formatting src/commands/projects/link.ts	Imported picocolors and applied color/underline formatting to dashboard URL and "What's next" instructions; updated phrasing to reference Claude Code and Cursor; preserved existing control flow and failure handling.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix(link): install agent skills in the template directory, not the parent #64 — Modifies src/commands/projects/link.ts and updates link flow messaging, closely related to these formatting/text changes.

Suggested reviewers

• jwfing
• CarmenDou

Poem

🐰 I hopped through code with colors bright,

cyan commands and green delight,
Underlined links that point the way,
Small changes, cheerful CLI day! 🎨✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: polishing the 'What's next' block with numbered steps, colorization, and a single copy-paste command, which aligns with the changeset in link.ts and the addition of picocolors dependency.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch polish/link-next-steps

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

src/commands/projects/link.ts (1)

268-268: Consider consistent dashboard URL styling across success branches.

Line 268 underlines the URL in the template path, but the non-template path (Line 287) remains plain. Unifying this would make output behavior more consistent.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/commands/projects/link.ts` at line 268, The dashboard URL is styled with
pc.underline in one success branch but left plain in the other, producing
inconsistent output; find the clack.log.step calls that output `Dashboard:
${dashboardUrl}` (both the template and non-template success branches) and make
them consistent by applying the same styling — e.g., change the plain
`Dashboard: ${dashboardUrl}` call to `Dashboard: ${pc.underline(dashboardUrl)}`
(or remove underline from the other branch) so both branches use the same
formatting; ensure you import/retain `pc` usage if needed and run the command to
verify consistent output.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/commands/projects/link.ts`:
- Line 268: The dashboard URL is styled with pc.underline in one success branch
but left plain in the other, producing inconsistent output; find the
clack.log.step calls that output `Dashboard: ${dashboardUrl}` (both the template
and non-template success branches) and make them consistent by applying the same
styling — e.g., change the plain `Dashboard: ${dashboardUrl}` call to
`Dashboard: ${pc.underline(dashboardUrl)}` (or remove underline from the other
branch) so both branches use the same formatting; ensure you import/retain `pc`
usage if needed and run the command to verify consistent output.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8b3e329c-fa4a-427d-8d0a-ef05b8c4761f

📥 Commits

Reviewing files that changed from the base of the PR and between 406c097 and c679ac3.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json
• src/commands/projects/link.ts