Skip to content

fix(shape-section): Section title with '&' generate unrecongized folder. Explicitly document the " & " → "-and-" conversion in the section-id instructions.#50

Open
nicolas-bastien wants to merge 1 commit intobuildermethods:mainfrom
nicolas-bastien:fix/shape-section-slug-ampersand-rule
Open

fix(shape-section): Section title with '&' generate unrecongized folder. Explicitly document the " & " → "-and-" conversion in the section-id instructions.#50
nicolas-bastien wants to merge 1 commit intobuildermethods:mainfrom
nicolas-bastien:fix/shape-section-slug-ampersand-rule

Conversation

@nicolas-bastien
Copy link
Copy Markdown

Summary

The shape-section command prompt described section-id slugging as "lowercase, hyphens instead of spaces" — omitting the " & " → "-and-" conversion that slugify() already applies. As a result, the AI creates folders like composants-ui instead of composants-and-ui, breaking section
resolution at runtime.

Fix: document the & rule explicitly in the section-id note, with a concrete example tied to slugify().

Linked item

  • Implements:

Checklist

  • Linked to related Issue/Discussion
  • Documented steps to test (below)
  • Drafted "how to use" docs (if this adds new behavior)
  • Backwards compatibility considered (notes if applicable)

Documented steps to test

  1. Run /shape-section on a section whose title contains & (e.g. "Composants & UI")
  2. Verify the generated folder is product/sections/composants-and-ui/ (not composants-ui/)
  3. Open the app and confirm the section page resolves correctly at /sections/composants-and-ui

Notes for reviewers

Prompt-only change, no app code touched. The app-side fix (slugify handling &) was already merged in 5f773b4 — this closes the gap on the prompt side.

…er. Explicitly document the " & " → "-and-" conversion in the section-id instructions.
@nicolas-bastien
Copy link
Copy Markdown
Author

@CasJam I found this bug while following your tutorial.

Is this the format of contribution you looking for ?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant