Remix

Make your own version of ToolTok Discovery Studio

Edit the prompt below and generate a customized version in seconds.

Original by azzam tozlok

Describe your app

BUILD A COMPLETE FULL-STACK APP CALLED **TOOLTOK**

Tagline: **“Scroll tools. Make them yours.”**

## CORE IDEA

TOOLTOK is NOT a video/social-media app. It is a TikTok-style vertical discovery feed for **functional digital tools**.

Users:

**SCROLL → DISCOVER → USE → EDIT → AI → PERSONALIZE → SAVE**

Every tool must have a prominent **EDIT TOOL** button. Users can describe changes in normal language and receive a genuinely modified, personalized version.

**NEVER fake AI, fake functionality, fake editing, or success messages for changes that did not actually happen.**

---

## DESIGN

Create a premium futuristic dark-first UI:

* dark background
* glassmorphism, subtle gradients/glows
* rounded cards
* premium typography
* smooth scrolling and micro-interactions
* polished animations
* excellent spacing
* responsive/touch-friendly layouts

Do NOT make it look like a generic dashboard or copy TikTok branding.

---

## VERTICAL TOOL FEED

The Home screen is a full-screen vertical snap-scrolling feed. Each tool occupies a large section and is immediately usable.

Every card includes:

* name
* description
* category
* functional interface
* **EDIT TOOL**
* Favorite
* Expand/fullscreen
* More/options

Support iPhone, Android, iPad/tablets and desktop. Support touch, mouse wheel and trackpad. Use lazy loading and efficient rendering.

---

## 50 INITIAL TOOLS

Create approximately 50 REAL functional tools:

**EVERYDAY:** Calculator, Unit Converter, Percentage Calculator, Time Calculator, Date Calculator, Stopwatch, Countdown Timer, Random Generator, Decision Maker, Checklist Maker.

**SCHOOL:** Math Helper, Science Helper, Quiz Generator, Flashcard Generator, Study Planner, Essay Helper, Summarizer, Citation Helper, Word Counter, Grade Calculator.

**WRITING:** Email Writer, Story Generator, Report Generator, Grammar Checker, Rewriter, Text Shortener, Text Expander, Tone Changer, Brainstorm Generator, Speech Writer.

**CREATIVE:** Image Generator, Image Editor, Logo Maker, Poster Maker, Color Palette Generator, Name Generator, Character Creator, Story Idea Generator, Thumbnail Concept Generator, Meme Generator.

**PRODUCTIVITY:** To-Do List, Goal Planner, Daily Planner, Habit Planner, Project Planner, Meeting Notes, Trip Planner, Packing List, Recipe Generator, Budget Planner.

No placeholder cards. If a feature requires an unavailable external service, do not pretend it works.

---

## TOOL SYSTEM

Do NOT build 50 unrelated pages. Create a reusable Tool System.

Each tool needs a structured **Tool Manifest** containing:

`id, name, description, category, version, components, capabilities, state, inputs, outputs, actions, settings, editableProperties, validationRules`

The editor must be able to understand the selected tool's actual structure and functionality.

Different tools must have different semantics. A calculator, stopwatch, quiz, recipe generator and planner must not be treated as identical generic components.

---

# EDIT TOOL — MOST IMPORTANT FEATURE

Every tool MUST have **EDIT TOOL**.

When pressed, open a dedicated Tool Editor and pass the selected tool's complete manifest/context to the AI.

The AI must know exactly which tool it is editing.

Editor includes:

* selected tool/version
* live preview
* natural-language input
* Analyze
* Make It Better
* Preview Changes
* Apply Changes
* Cancel

Users can say things like:

“Make this calculator futuristic.”

“Add scientific functions and graphing.”

“Make it better on iPad.”

“Move history to the right.”

“Add dark/light mode.”

“Keep normal mode and add an advanced mode.”

No programming knowledge should be required.

---

## AI EDITING PIPELINE

Do NOT make Edit Tool a generic chatbot.

Use:

**Selected Tool → Manifest → User Request → AI Analysis → Structured Change Plan → Validation → Preview → Apply → Test → New Version**

The AI receives the selected tool's UI, components, state, actions, functionality, settings, editable properties and previous versions.

Supported change types:

ADD, REMOVE, MODIFY, REPLACE, REDESIGN, FIX, IMPROVE, REORGANIZE, REFACTOR, CHANGE BEHAVIOR, CHANGE APPEARANCE, ADD/REMOVE MODE, CHANGE SETTINGS.

---

## STRUCTURED MODIFICATION ENGINE

Convert AI decisions into safe operations such as:

`ADD_COMPONENT`
`REMOVE_COMPONENT`
`MOVE_COMPONENT`
`REPLACE_COMPONENT`
`CHANGE_STYLE`
`CHANGE_LAYOUT`
`ADD_FEATURE`
`REMOVE_FEATURE`
`CHANGE_BEHAVIOR`
`ADD_MODE`
`CHANGE_TEXT`
`CHANGE_SETTING`
`FIX_LOGIC`
`ADD_VALIDATION`

Validate operations before applying them.

For substantial edits, show **CURRENT vs PROPOSED** and provide:

**APPLY / EDIT REQUEST / CANCEL**

The actual personalized tool must change. Do NOT merely save a description saying a feature was added.

---

## VERSIONING + UNDO

Never destroy the original tool.

Every edit creates a version. Support:

* view/rename/compare versions
* restore version
* undo latest change

If validation fails, keep the previous working version active.

---

## PERSONALIZATION

User A editing Calculator must NEVER change User B's Calculator.

Use:

**Global Tool → User Tool Instance → Tool Version → Changes**

Use proper server-side authorization/RLS where supported.

Add **MAKE MY VERSION** to clone a global tool.

---

## MAKE IT BETTER

Every tool should have **MAKE IT BETTER**.

Analyze the current tool and suggest improvements. Do not automatically destroy the existing design. Let the user choose which improvements to apply.

---

## MY TOOLS / FAVORITES / SEARCH

User account should include:

* Profile
* Favorites
* My Tools
* Recently Used
* Settings

Search by tool name, category, description and capabilities.

Categories:

**Everyday / School / Writing / Creative / Productivity**

Optional discovery sections:

**For You / Popular / New / Favorites**

Keep the focus on tools, not social media.

---

## FULLSCREEN + SHARING

Every tool supports fullscreen/expand mode.

Customized tools may be shared. Shared versions are read-only by default. Another user can select **MAKE MY VERSION**.

Never expose private data.

---

## AUTH + DATABASE

Implement real authentication and persistent backend data.

Use the platform's built-in database/backend where possible.

Conceptual entities:

`users, tools, user_tools, tool_versions, tool_changes, favorites, recent_tools, shared_tools, tool_settings`

Do not duplicate equivalent platform structures.

---

## AI ASSISTANT

Include a general assistant that understands the currently opened tool.

It can explain tools, suggest improvements, troubleshoot, create change plans and apply supported changes.

It must use actual tool context, not generic responses.

---

## NO CREDIT SYSTEM

Do NOT create credits, coins, tokens, AI balances, “Give More,” purchases, or fake usage counters inside the app.

## NO NORMAL-USER API KEYS

Never ask users for OpenAI, Gemini, Anthropic or other API keys.

Use the platform's available AI infrastructure. Keep administrator secrets server-side and never expose them to clients.

---

## SECURITY

The AI editor can only modify authorized user versions.

Never allow it to:

* access other users' private data
* expose secrets/environment variables
* bypass authentication
* change authorization
* execute arbitrary dangerous server commands
* modify unrelated users

Never trust client-side user IDs.

---

## PERFORMANCE + RESPONSIVENESS

Use lazy loading, optimized assets, efficient state management and virtualization where useful.

Do not initialize expensive AI/image functionality for every tool simultaneously.

Make iPad a first-class target:

* large touch targets
* smooth gestures
* no horizontal overflow
* excellent tablet layouts
* fullscreen editing
* keyboard support
* landscape support where useful

Desktop should have an intentional layout.

---

# DEMO ACCEPTANCE TEST

Open **Calculator → EDIT TOOL** and request:

“Make this a futuristic scientific calculator. Keep the basic calculator and add scientific functions, fractions, history, memory buttons, graphing mode, keyboard shortcuts, unit conversion, dark/light themes, smoother animations, and a better tablet layout.”

The system MUST:

1. Understand Calculator.
2. Generate a structured plan.
3. Show proposed changes.
4. Apply supported changes.
5. Actually modify the tool.
6. Create a new version.
7. Validate it.
8. Display the working result.
9. Allow undo/restore.

Also test:

**Quiz Generator:** difficulty, timer, streaks, explanations and mistake review.

**Stopwatch:** laps, fullscreen display, themes and session history.

**Recipe Generator:** serving adjustment, metric/imperial conversion, ingredient scaling, dietary filters and shopping list.

These must produce REAL functionality.

---

## BUILD ORDER

1. App shell + vertical feed
2. Tool registry + 50 tools
3. Authentication + database
4. Favorites + My Tools
5. Tool Editor
6. Tool Manifest/context system
7. AI change planning
8. Real modification engine
9. Preview + Apply
10. Validation + rollback
11. Version history
12. Responsive/performance polish

Keep Feed, Tool Registry, Tool Renderer, Editor, AI Context Builder, Change Planner, Modification Engine, Preview, Validation, Versioning, Auth, Favorites, Search and Settings modular.

---

# FINAL ACCEPTANCE RULE

TOOLTOK is NOT complete because it has a beautiful feed, 50 cards or an AI chat.

It is complete ONLY when:

**USER → opens tool → EDIT TOOL → describes change → AI understands the specific tool → creates plan → previews → applies → tool genuinely changes → functionality works → version saves → previous version can be restored.**

Prioritize REAL functionality over visual imitation.

**TOOLTOK = DISCOVER SOFTWARE, THEN MAKE IT YOURS.**

Free to use. No credit card required.