The organized hub for everything WertWorks is building.

Music bots can get messy when queue controls, radio stations, playlist imports, and playback state all live in separate commands with unclear feedback.

Build a focused Discord music bot with reliable queue state, button-based playback controls, radio preset configuration, and optional Spotify metadata support that resolves tracks into playable sources.

• Plays music from YouTube search, direct URLs, and YouTube playlists.
• Live radio mode with preset dropdowns, station lookup, and direct stream URLs.
• Spotify track, album, and playlist link imports using metadata lookup.

Add slash-command versions of core controls and small tests around query parsing and URL handling.

A community server needs small utilities that fit its culture: self-role setup, archive saves, status checks, voice moments, and game-related helpers without forcing moderators to run everything manually.

Use a modular Python Discord bot with command cogs, environment-based setup, OpenAI text and TTS support, reaction-based archiving, tarot slash commands, and optional Valorant API integration.

• Prefix commands for diagnostics, bot info, owner restart, AI voice omens, and role setup.
• Reaction-based archive flow for saving messages into an archive channel.
• Slash-command tarot reads with single-card and spread options.

Keep polishing the active modules and document which parked cogs are intentionally inactive.

Server rituals and timed reminders are easy to forget when they depend on someone manually joining voice, posting timestamps, or tracking a countdown in chat.

Keep the bot intentionally small: configure one voice channel, run a predictable hourly bell loop, expose simple admin commands, and provide timestamp and timer utilities for members.

• Rings a bell at the top of each hour when users are in the configured voice channel.
• Manual `!bell` command with public or restricted access modes.
• Admin `!clock on|off|status` controls for hourly ringing.

Keep the setup checklist tight and improve restart behavior around active timers.

Job searches get messy when leads, resumes, contacts, follow-up dates, and application notes are spread across tabs, documents, and memory.

Use a structured dashboard that keeps application status, role context, follow-up tasks, and notes visible without turning the process into another scattered system.

• Status tracking for leads, applications, interviews, offers, and rejections.
• Role notes for pay, location, schedule, contacts, and requirements.
• Follow-up dates and next actions for each opportunity.

Connect persistence to a real backend and add reminder exports.

Application materials can split across browser bookmarks, file names, screenshots, saved postings, and notes that are hard to connect later.

Create a repeatable record for each application with the posting link, resume version, cover letter notes, contact details, and follow-up plan.

• Application record structure for links, contacts, and notes.
• Document version notes for resume and cover letter variants.
• Follow-up checklist for each role.

Define the final record fields and connect them to the job dashboard.

Resume and cover letter updates become repetitive when every role needs a slightly different angle but the source material is scattered.

Create a small toolkit for reusable summaries, targeted notes, and role-specific draft material that can be copied or refined as needed.

• Reusable professional summary area.
• Role-specific notes for targeted applications.
• Cover letter drafting checklist.

Add role templates and connect the toolkit to application records.

Small sites often start as disconnected pages instead of a useful system with clear routes, shared content, and honest calls to action.

Build around reusable sections, central data, clear navigation, and pages that explain what exists, what is in progress, and what comes next.

• Next.js App Router site structure.
• Reusable cards, page intros, forms, and project components.
• Shared profile, navigation, and project data.

Add more concrete screenshots and document finished site examples.

Recurring workflows can fail when steps live in memory and there is no visible handoff, status, or verification process.

Translate checklist discipline into software patterns: clear steps, responsible status, review points, and documented next actions.

• Checklist-first workflow planning.
• Status and handoff concepts inspired by aviation maintenance habits.
• Use-case notes for job tools, bots, aerial planning, and site operations.

Prototype one checklist flow inside an automation or job-tools page.

Future aerial work needs clear boundaries before it is presented publicly: licensing, equipment, safety, insurance, operating area, intake, and legal requirements all matter.

Keep aerial planning in a dedicated roadmap that states what is being researched, what is required before launch, and what conversations are appropriate today.

• Launch-status language that avoids claiming active commercial service.
• Possible future service categories and operating boundaries.
• Part 107, insurance, safety, equipment, and intake planning.

Define equipment requirements, licensing timeline, and intake checklist.