Slack Pro

Build me a focused online communities and team communication workflow for the personal core of Slack Pro. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose. Model the inputs, state transitions, and outputs named in this online communities and team communication prompt; keep source IDs and timestamps.
- Paid product context: Run a small private team chat with channels, threads, files, and search. Build only this DIY scope: Run a small private team chat with channels, threads, file sharing, and search, and keep membership and moderation under the owner's control.
- Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations.
- Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
- Add owner-controlled retention, account deletion, backup, restore, and health checks.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; public HTTPS deployment.
- Recovery: Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A removed post must not reappear from a delayed notification; permission checks must apply to every read and write.
- Out of scope: existing team network, integrations, push delivery, enterprise controls, and global reliability; network effects. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Slack Pro

## Project scope
Run a small private team chat with channels, threads, file sharing, and search, and keep membership and moderation under the owner's control.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Slack Pro, run a small private team chat with channels, threads, files, and search. The hard boundary is existing team network, integrations, push delivery, enterprise controls, and global reliability, plus network, moderation, and communication infrastructure.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Docker
- PostgreSQL
- public HTTPS deployment
- email provider
- object storage for attachments

## Stack and architecture
- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose.
- Model the inputs, state transitions, and outputs named in this online communities and team communication prompt; keep source IDs and timestamps.
- Interface for this online communities and team communication workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: existing team network, integrations, push delivery, enterprise controls, and global reliability.

## Agent implementation rules
- Project rule, data: Model the inputs, state transitions, and outputs named in this online communities and team communication prompt; keep source IDs and timestamps.
- Project rule, behavior: Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations.
- Project rule, recovery: Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this online communities and team communication operation with sample or user-owned data: Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations.
- Show a concrete result or export: Provide email digests, browser notifications, search, pinned content, and member export.
- State the practical limit: existing team network, integrations, push delivery, enterprise controls, and global reliability.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose. Model the inputs, state transitions, and outputs named in this online communities and team communication prompt; keep source IDs and timestamps.
2. Phase 2, implement: Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations.
3. Phase 3, implement: Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
4. Phase 4, review and output: Add owner-controlled retention, account deletion, backup, restore, and health checks. Provide email digests, browser notifications, search, pinned content, and member export.
5. Phase 5, recovery and acceptance: Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log. Verify this invariant with a saved fixture: A removed post must not reappear from a delayed notification; permission checks must apply to every read and write. State the practical limit: existing team network, integrations, push delivery, enterprise controls, and global reliability.

## Paid-product capabilities outside this build
- existing team network, integrations, push delivery, enterprise controls, and global reliability
- network effects
- native mobile apps
- video and voice infrastructure
- enterprise moderation and discovery

## Implementation prompt
Build me a focused online communities and team communication workflow for the personal core of Slack Pro. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose. Model the inputs, state transitions, and outputs named in this online communities and team communication prompt; keep source IDs and timestamps.
- Paid product context: Run a small private team chat with channels, threads, files, and search. Build only this DIY scope: Run a small private team chat with channels, threads, file sharing, and search, and keep membership and moderation under the owner's control.
- Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations.
- Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
- Add owner-controlled retention, account deletion, backup, restore, and health checks.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; public HTTPS deployment.
- Recovery: Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A removed post must not reappear from a delayed notification; permission checks must apply to every read and write.
- Out of scope: existing team network, integrations, push delivery, enterprise controls, and global reliability; network effects. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.