docs(here-now): add House Rules — authenticated publish by default, edit in place to keep the URL

[Edouardtriet]

Adds a short House Rules block to the here-now SKILL.md, capturing two defaults that came out of real agent usage:

1. Assume logged in — when credentials are present, just publish authenticated and return the slug/URL ("code") instead of defaulting to --anon + the claim dance.
2. Edits stay on the same link — to update an already-published site, re-publish in place with publish update-site <slug> rather than re-running publish dir or delete+recreate. Both of the latter mint a new slug, and since deleted slugs are permanently reserved, the original URL is lost.

The second one bit us in practice: an "update" via publish dir --slug <existing> silently produced a new site, and trying to reclaim the old slug by deleting + recreating failed (slug reserved), churning the public URL twice. The note steers agents to update-site so the shared link stays stable.

Docs-only change to the source library/cloud/here-now/SKILL.md; the generated skill mirrors regenerate post-merge. No code changes.

[greptile-apps]

Greptile Summary

This docs-only PR adds a House Rules section to library/cloud/here-now/SKILL.md that codifies two agent defaults: prefer authenticated publish over anonymous and use publish update-site <slug> to edit a live site in place instead of delete-and-recreate.

• Adds two default-behavior rules to steer agents away from --anon publish and from inadvertently minting new slugs during updates.
• The new section is well-placed and clearly worded, but an existing recipe (### Publish a folder and keep it permanently) still demonstrates the --anon + claim-dance flow that House Rule feat(dub): add dub.co cli (dub-pp-cli) #1 explicitly prohibits by default, creating a direct contradiction in the same file.

Confidence Score: 3/5

The House Rules section itself is clear and useful, but the unchanged anonymous-publish recipe in the same file now gives agents directly contradictory instructions about when to use --anon.

The new House Rules section correctly establishes authenticated-first publish as the default, but the pre-existing Publish a folder and keep it permanently recipe still shows the --anon + claim-dance flow without any qualifier that it applies only when anonymous publish is explicitly requested. An agent reading both sections encounters conflicting directives — the House Rule says never use --anon by default, while the recipe demonstrates exactly that pattern. The recipe should be updated or annotated before this merges to avoid confusing agents.

library/cloud/here-now/SKILL.md — the Recipes section needs the anonymous-publish recipe reconciled with the new House Rule #1.

Important Files Changed

Filename	Overview
library/cloud/here-now/SKILL.md	Adds a House Rules section with two agent defaults (authenticated-first publish and in-place updates via update-site), but the existing anonymous-publish recipe now directly contradicts House Rule #1, leaving agents with conflicting guidance in the same file.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Agent wants to publish] --> B{Credentials present?}
    B -- Yes --> C["publish dir <path> (authenticated)"]
    B -- No --> D["Ask user / use --anon only if explicitly requested"]
    C --> E[Returns slug + URL]
    E --> F{Is this an edit to existing site?}
    F -- No --> G[Hand back slug/URL as result]
    F -- Yes --> H["publish update-site <slug> (in-place)"]
    H --> I[Same URL preserved]
    D -.->|OLD recipe still shown| J["publish dir --anon + claims expiring (contradicts House Rule 1)"]
    style J fill:#ffcccc,stroke:#cc0000

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Agent wants to publish] --> B{Credentials present?}
    B -- Yes --> C["publish dir <path> (authenticated)"]
    B -- No --> D["Ask user / use --anon only if explicitly requested"]
    C --> E[Returns slug + URL]
    E --> F{Is this an edit to existing site?}
    F -- No --> G[Hand back slug/URL as result]
    F -- Yes --> H["publish update-site <slug> (in-place)"]
    H --> I[Same URL preserved]
    D -.->|OLD recipe still shown| J["publish dir --anon + claims expiring (contradicts House Rule 1)"]
    style J fill:#ffcccc,stroke:#cc0000

Loading

Comments Outside Diff (1)

1. library/cloud/here-now/SKILL.md, line 197-201 (link)

   Recipe contradicts House Rule feat(dub): add dub.co cli (dub-pp-cli) #1

   The ### Publish a folder and keep it permanently recipe (line 198) uses --anon and the claim dance — precisely what House Rule feat(dub): add dub.co cli (dub-pp-cli) #1 now tells agents not to do by default. An agent that reads both sections has directly contradictory instructions: the House Rule says "do not use --anon ... unless explicitly asked", but this recipe demonstrates exactly that flow with no such qualifier. A naive agent scanning for a publish recipe could land here and ignore the House Rule entirely.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

   

_{Reviews (1): Last reviewed commit: "docs(here-now): add House Rules — defaul..." | Re-trigger Greptile}