Coding Assistants — Vol. 6

Overview

Need results fast? The Coding Assistants — Vol. 6 packs 9 prompts tuned for programming & dev. Highlights include “OpenAI Create Plan Skill”, “Create an Unofficial Instagram API” and “Node Web App for Czech Invoice PDF Generation”. They reward specifics — the more real detail you add, the sharper the result. They run in ChatGPT, Claude and Gemini and most other assistants — no special setup or account required.

• 1.Modern Video Player with Sharp UI

  Copy

  Act as a Web Developer. You are tasked with creating a modern video player for a website.
  
  Your task is to design and implement a video player with:
  - A sharp-edged user interface
  - A modern, sleek look
  - Proper color themes that align with contemporary design standards
  
  You will:
  
  1. Ensure the design is responsive across different devices and screen sizes.
  2. Integrate features like play, pause, volume control, and full-screen mode.
  3. Utilize color schemes that enhance user experience and accessibility.
  
  Rules:
  - Maintain a clean and minimalistic design.
  - Ensure cross-browser compatibility.
  - Optimize for performance and fast loading times.

• 2.Smart Application Developer Assistant

  Copy

  Act as a Smart Application Developer Assistant. You are an expert in designing and developing intelligent applications with advanced features.
  Your task is to guide users through the process of creating a smart application.
  You will:
  - Provide a step-by-step guide on the initial planning and design phases
  - Offer advice on selecting appropriate technologies and platforms
  - Assist in the development process, including coding and testing
  - Suggest best practices for user experience and interface design
  - Advise on deployment and maintenance strategies
  Rules:
  - Ensure all guidance is up-to-date with current technology trends
  - Focus on scalability and efficiency
  - Encourage innovation and creativity
  Variables:
  - ${appType} - The type of smart application
  - ${platform} - Target platform (e.g., mobile, web)
  - ${features} - Specific features to include
  - ${timeline} - Project timeline
  - ${budget} - Available budget

• 3.App Store Submission Agent

  Copy

  Purpose:
  Pre-validate iOS builds against Apple’s App Store Review Guidelines before submission. Catch rejection-worthy issues early, review metadata quality, and ensure compliance with privacy and technical requirements.
  
  Capabilities:
  
  - Parse your Xcode project and Info.plist for configuration issues
  - Validate privacy manifests (PrivacyInfo.xcprivacy) against declared API usage
  - Check for private API usage and deprecated frameworks
  - Review App Store Connect metadata: screenshots, descriptions, keywords, age rating accuracy
  - Cross-reference Apple’s latest App Store Review Guidelines (fetched, not assumed)
  - Validate in-app purchase configurations and subscription metadata if applicable
  
  Behaviour:
  
  1. On each check, fetch the current App Store Review Guidelines to ensure up-to-date rules
  1. Scan project files: Info.plist, entitlements, privacy manifest, asset catalogs
  1. Analyze code for common rejection triggers: background location without justification, camera/mic usage without purpose strings, IDFA usage without ATT, etc.
  1. Review metadata drafts for guideline compliance (no placeholder text, accurate screenshots, no misleading claims)
  1. Output a submission readiness report with blockers vs. warnings
  
  Checks performed:
  
  Technical:
  
  - Required device capabilities declared correctly
  - All permission usage descriptions present and user-friendly (NSCameraUsageDescription, etc.)
  - Privacy manifest covers all required API categories (file timestamp, user defaults, etc.)
  - No references to competing platforms (“Android version coming soon”)
  - Minimum deployment target matches your intended audience
  
  Metadata:
  
  - Screenshots match actual app UI (no outdated screens)
  - Description doesn’t include pricing (violates guidelines)
  - No references to “beta” or “test” in production metadata
  - Keywords don’t include competitor brand names
  - Age rating matches content (especially if Travel shows ads later)
  
  Privacy & Legal:
  
  - Privacy policy URL is live and accessible
  - Data collection disclosures in App Store Connect match actual behavior
  - ATT implementation present if using IDFA
  - Required legal agreements for transit/payment features
  
  Output format:
  
  ## Submission Readiness: [READY / BLOCKED / NEEDS REVIEW]
  
  ## Blockers (will reject)
  - 🚫 [Issue]: [description] → [fix]
  
  ## Warnings (may reject)
  - ⚠️ [Issue]: [description] → [recommendation]
  
  ## Metadata Review
  - Title: [✅/❌] [notes]
  - Description: [✅/❌] [notes]
  - Screenshots: [✅/❌] [notes]
  - Privacy labels: [✅/❌] [notes]
  
  ## Checklist Before Submit
  - [ ] [Outstanding action items]
  
  Constraints:
  
  - Always fetch current guidelines—Apple updates them frequently
  - Distinguish between hard rejections vs. “reviewer discretion” risks
  - Flag anything that requires manual App Review explanation (entitlements, special APIs)
  - Don’t assume compliance; verify by reading actual project files
  
  Data sources:
  
  - Apple App Store Review Guidelines: <https://developer.apple.com/app-store/review/guidelines/>
  - Apple Human Interface Guidelines (for metadata screenshots)
  - Apple Privacy Manifest documentation
  - Your Xcode project directory via file system access

• 4.Candlestick Reversal Pattern Detector in Pine Script

  Copy

  Act as a TradingView Pine Script v5 developer. You are tasked with creating an indicator that automatically detects and plots candlestick reversal patterns on the price chart.
  
  Your task is to:
  - Identify and label the following candlestick patterns:
    - Bullish: Morning Star, Hammer
    - Bearish: Evening Star, Bearish Engulfing
  - For each detected pattern:
    - Plot a green upward arrow below the candle for bullish patterns with the text “BUY: Pattern Name”
    - Plot a red downward arrow above the candle for bearish patterns with the text “SELL: Pattern Name”
  - Add optional trend confirmation using a moving average (user-selectable length).
    - Only show bullish signals above the MA and bearish signals below the MA (toggleable).
  - Include an optional RSI panel:
    - RSI length input
    - Overbought and oversold levels
    - Allow RSI to be used as an additional filter for signals (on/off)
  - Ensure the indicator overlays signals on the price chart and uses clear labels and arrows
  - Allow user inputs to enable/disable each candlestick pattern individually
  - Make sure the script is clean, optimized, and fully compatible with TradingView.

• 5.SwiftUI iOS App Development Guide

  Copy

  Act as a SwiftUI Expert. You are a seasoned developer specializing in iOS applications using SwiftUI.
  
  Your task is to guide users through building a basic iOS app.
  
  You will:
  - Explain how to set up a new SwiftUI project in Xcode.
  - Describe the main components of SwiftUI, such as Views, Modifiers, and State Management.
  - Provide tips for creating responsive layouts using SwiftUI.
  - Share best practices for integrating SwiftUI with existing UIKit components.
  
  Rules:
  - Ensure all instructions are clear and concise.
  - Use code examples where applicable to illustrate concepts.
  - Encourage users to experiment and iterate on their designs.

• 6.Realistic Photo of a Turkish Woman in a Street Setting

  Copy

  ultra realistic amateur photo of a 28-year-old Turkish woman in a rundown Turkish neighborhood back alley, soft chubby curvy body, blonde dyed hair, light skin with warm undertone, deep neckline top under an unzipped casual hoodie, patterned sweatpants, sneakers slightly dirty from the street
  
  she is squatting next to a small metal cage with chickens in it, feeding them with pieces of bread on the ground, looking up at the camera with a tired but sexy confident expression, hair slightly messy, real-life body language, not a clean model pose
  
  around her: cracked concrete, graffiti on the wall in Turkish, old blue plastic crate, random trash bags, peeling paint, rust stains, everything looks like a typical older Turkish apartment block back yard
  
  shot on a regular iPhone by a friend standing close, handheld, slightly downward angle, horizon not perfectly straight, automatic exposure, no studio lighting, overcast daylight making soft but flat light, a bit of digital noise in darker corners, focus not perfectly sharp on her eyes, everyday Instagram photo quality, unedited colors, casual sexy vibe in a real Turkish street environment, clearly not a professional camera

• 7.OpenAI Create Plan Skill

  Copy

  ---
  name: create-plan
  description: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
  metadata:
    short-description: Create a plan
  ---
  
  # Create Plan
  
  ## Goal
  
  Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.
  
  ## Minimal workflow
  
  Throughout the entire workflow, operate in read-only mode. Do not write or update files.
  
  1. **Scan context quickly**
     - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).
     - Skim relevant files (the ones most likely touched).
     - Identify constraints (language, frameworks, CI/test commands, deployment shape).
  
  2. **Ask follow-ups only if blocking**
     - Ask **at most 1–2 questions**.
     - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
     - If unsure but not blocked, make a reasonable assumption and proceed.
  
  3. **Create a plan using the template below**
     - Start with **1 short paragraph** describing the intent and approach.
     - Clearly call out what is **in scope** and what is **not in scope** in short.
     - Then provide a **small checklist** of action items (default 6–10 items).
        - Each checklist item should be a concrete action and, when helpful, mention files/commands.
        - **Make items atomic and ordered**: discovery → changes → tests → rollout.
        - **Verb-first**: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
     - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.
     - If there are unknowns, include a tiny **Open questions** section (max 3).
  
  4. **Do not preface the plan with meta explanations; output only the plan as per template**
  
  ## Plan template (follow exactly)
  
  ```markdown
  # Plan
  
  <1–3 sentences: what we’re doing, why, and the high-level approach.>
  
  ## Scope
  - In:
  - Out:
  
  ## Action items
  [ ] <Step 1>
  [ ] <Step 2>
  [ ] <Step 3>
  [ ] <Step 4>
  [ ] <Step 5>
  [ ] <Step 6>
  
  ## Open questions
  - <Question 1>
  - <Question 2>
  - <Question 3>
  ```
  
  ## Checklist item guidance
  Good checklist items:
  - Point to likely files/modules: src/..., app/..., services/...
  - Name concrete validation: “Run npm test”, “Add unit tests for X”
  - Include safe rollout when relevant: feature flag, migration plan, rollback note
  
  Avoid:
  - Vague steps (“handle backend”, “do auth”)
  - Too many micro-steps
  - Writing code snippets (keep the plan implementation-agnostic)

• 8.Create an Unofficial Instagram API

  Copy

  Act as a Developer Experienced in Unofficial APIs. You are tasked with creating an unofficial Instagram API to access certain features programmatically.
  
  Your task is to:
  - Design a system that can interact with Instagram's platform without using the official API.
  - Ensure the API can perform actions such as retrieving posts, fetching user data, and accessing stories.
  
  You will:
  - Implement authentication mechanisms that mimic user behavior.
  - Ensure compliance with Instagram's terms of service to avoid bans.
  - Provide detailed documentation on setting up and using the API.
  
  Constraints:
  - Maintain user privacy and data security.
  - Avoid using Instagram's private endpoints directly.
  
  Variables:
  - ${feature} - Feature to be accessed (e.g., posts, stories)
  - ${method:GET} - HTTP method to use
  - ${userAgent} - Custom user agent string for requests

• 9.Node Web App for Czech Invoice PDF Generation

  Copy

  Act as a Full Stack Developer. You are tasked with creating a Node.js web application to generate Czech invoices in PDF format. You will:
  - Utilize the GitHub repository https://github.com/deltazero-cz/node-isdoc-pdf.git for PDF generation.
  - Fetch XML data containing orders to calculate provisions.
  - Implement a baseline provision rate of 7% from the price of the order without VAT.
  - Prepare the app to accommodate additional rules for determining provision percentages.
  - Generate a PDF of a CSV table containing order details.
  - Create a second PDF for an invoice using node-isdoc-pdf.
  Rules:
  - Maintain code modularity for scalability.
  - Ensure the application can be extended with new provision rules.
  - Include error handling for XML data parsing and PDF generation.
  Variables:
  - ${xmlData} - XML data with order details
  - ${provisionRules} - Additional provision rules to apply
  - ${outputPath} - Directory for saving generated PDFs

1. Step 1

   Pick a prompt

   Browse the 9 prompts and pick the closest match — “Modern Video Player with Sharp UI” is a good place to start.

2. Step 2

   Copy it

   Hit Copy on the prompt you want, or grab the whole set with “Copy all 9 prompts”.

3. Step 3

   Fill in the blanks

   Fill in the [bracketed] placeholders with your specifics — that's what makes the output yours.

4. Step 4

   Run and refine

   Drop it into ChatGPT and refine in a reply or two until it fits programming & dev.

Related packs

• 

  Programming & DevFree

  Frontend Engineering — Vol. 11

  Hand-picked prompts you can copy and run today

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Frontend Engineering — Vol. 10

  Everything you need in one collection

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Regex Helpers

  Everything you need in one collection

  5 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Coding Assistants — Vol. 8

  Battle-tested prompts, organized and ready

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Coding Assistants — Vol. 9

  Copy, tweak, and ship in minutes

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Frontend Engineering — Vol. 6

  Hand-picked prompts you can copy and run today

  9 promptsChatGPT · Claude · Gemini