Block · Collaboration

Comments

Adds a comment table attached to one of your tables (tasks, posts, lessons, listings) and a CommentThread component: replies nest under the comment they answer, typing @ suggests people to mention, authors can edit and delete their own comments, and new comments appear for everyone without a refresh. People are told in-app when they are mentioned or someone replies to them. Staff get a moderation list.

View the files

use_template { slug: "comments" } adds

Tables: comment
Components: CommentThread
Pages: /discussion, /comments-admin
Workflows: comment-notify
Rules: 4 on comment

What it adds to your app

Table comment: subject, parent, author, body, mentions. CommentThread component (threads, @mentions, edit, delete, live). A Discussion page and a staff moderation list. One workflow: notify mentions and replies.

Tables

comment subject_id, parent_id, author_id, body, mentions, edited_at, organisation_id

Workflows

comment-notify Tell people they were mentioned or replied to. On comment created

Components

CommentThread Threaded comments on one ‹attach_to› with replies, @mentions, edit and delete, updating live

Rules on every write

comment Write something before you post.
comment A reply belongs to the same thread as the comment it answers.
comment A comment keeps its author.
comment A comment belongs to the organisation of what it's about.

Where it attaches

Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.

Param	What it is	Example
`attach_to`	The table whose records people comment on.	`task`
`author_role`	The role whose people write comments (their own table is the author). Optional.	`member`
`org_field`	Optional: the ref on that table naming its organisation (from organisations-and-teams). Comments then belong to that organisation and only its members read them. Optional.	`organisation_id`

Use with your coding agent

Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
It applies to dev. Check it, then deploy when you are happy.

Prompt

Add the Comments template (slug "comments") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (attach_to: comment on; author_role: who comments; org_field: organisation (optional)).

MCP call

{
  "tool": "use_template",
  "arguments": {
    "slug": "comments",
    "project_id": "<your project id>",
    "params": {
      "attach_to": "task",
      "author_role": "member",
      "org_field": "organisation_id"
    },
    "dry_run": true
  }
}

CLI

appbricx templates use comments --param attach_to=task --param author_role=member --param org_field=organisation_id --dry-run

Your agent adds it. Appbricx runs it.

Start free All templates

Block · Collaboration

Comments

View the files

use_template { slug: "comments" } adds

Tables: comment
Components: CommentThread
Pages: /discussion, /comments-admin
Workflows: comment-notify
Rules: 4 on comment

What it adds to your app

Tables

comment subject_id, parent_id, author_id, body, mentions, edited_at, organisation_id

Workflows

comment-notify Tell people they were mentioned or replied to. On comment created

Components

CommentThread Threaded comments on one ‹attach_to› with replies, @mentions, edit and delete, updating live

Rules on every write

comment Write something before you post.
comment A reply belongs to the same thread as the comment it answers.
comment A comment keeps its author.
comment A comment belongs to the organisation of what it's about.

Where it attaches

Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.

Param	What it is	Example
`attach_to`	The table whose records people comment on.	`task`
`author_role`	The role whose people write comments (their own table is the author). Optional.	`member`
`org_field`	Optional: the ref on that table naming its organisation (from organisations-and-teams). Comments then belong to that organisation and only its members read them. Optional.	`organisation_id`

Use with your coding agent

Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
It applies to dev. Check it, then deploy when you are happy.

Prompt

Add the Comments template (slug "comments") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (attach_to: comment on; author_role: who comments; org_field: organisation (optional)).

MCP call

{
  "tool": "use_template",
  "arguments": {
    "slug": "comments",
    "project_id": "<your project id>",
    "params": {
      "attach_to": "task",
      "author_role": "member",
      "org_field": "organisation_id"
    },
    "dry_run": true
  }
}

CLI

appbricx templates use comments --param attach_to=task --param author_role=member --param org_field=organisation_id --dry-run

Your agent adds it. Appbricx runs it.

Start free All templates

Comments

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Organisations and teams

Booking calendar

Stripe subscriptions

Your agent adds it. Appbricx runs it.

Comments

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Organisations and teams

Booking calendar

Stripe subscriptions

Your agent adds it. Appbricx runs it.

Comments

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Goes well with

Organisations and teams

Booking calendar

Stripe subscriptions

Your agent adds it. Appbricx runs it.

Comments

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Goes well with

Organisations and teams

Booking calendar

Stripe subscriptions

Your agent adds it. Appbricx runs it.