Althera PromptsAlthera PromptsAlthera Prompts
BotsPromptsSkillsWorkflowsCategoriesTagsPromptmastersTaste
Developers
Login
CC0 2026 Althera Prompts
GitHub
All Tags

Pricing Prompts

8 prompts
Write Tier Descriptions
Text

Unlocking New Pricing Tiers

Write descriptions for three GitHub Sponsors tiers ($5, $25, $100) that offer increasing value and recognition to supporters.
PricingDescriptionsTiers
F@f
0
Student Tier
Text

Unlocking New Pricing Tiers

Create a special $1-2 student sponsorship tier with meaningful benefits that acknowledges their support while respecting their budget.
PricingAccessibilityStudents
F@f
0
Enterprise Sponsorship
Text

Unlocking New Pricing Tiers

Design enterprise-level sponsorship tiers ($500, $1000, $5000) with benefits like priority support, custom features, and brand visibility for my [project].
PricingEnterpriseTiers
F@f
0
Suggest Pricing Tiers
Text

Unlocking New Pricing Tiers

Suggest ideas for pricing tiers on GitHub Sponsors, including unique benefits at each level for individuals and companies.
PricingBenefitsTiers
F@f
0
SaaS Payment Plan Options
Text

Generate distinct payment plan cards for a SaaS application with a highlighted selected card and the most expensive option in the center.

Act as a website designer. You are tasked with creating payment plan options at the bottom of the homepage for a SaaS application. There will be three cards displayed horizontally:

- The most expensive card will be placed in the center to draw attention.
- Each card should have a distinct color scheme, with the selected card having a highlighted border to show it's currently selected.
- Ensure the design is responsive and visually appealing across all devices.

Variables you can use:
- selectedCardColor for the border color of the selected card.
- centerCard to indicate which plan is the most expensive.

Your task is to visually convey the pricing tiers effectively and attractively to users.
MarketingPricing
A@ahmettzorlutuna
0
Android AI App Security Specialist Task
Text

Act as an Android AI App Security Specialist. Implement secure configurations to protect API keys, prevent misuse, and establish a sustainable pricing model for your application.

Act as an Android AI App Security Specialist. You are responsible for implementing secure configurations to protect API keys, prevent misuse, and establish a sustainable pricing model for your application.

Your tasks include:

1. **Backend Proxy Configuration:**
   - Set up a minimal, secure proxy backend using services like Railway.app, Render.com, Vercel, or Firebase Cloud Functions.
   - Create a single endpoint to receive user messages and relay them to the AI API: POST/chat.
   - Ensure the API key is securely stored on the backend and never exposed in the client application.

2. **Android App Updates:**
   - Remove all API keys from the Android app codebase.
   - Use Retrofit or Ktor to connect directly to the backend proxy endpoint (e.g., https://albaroka.com/chat).
   - Ensure no hard-coded keys exist in BuildConfig or code.

3. **Pricing Model Implementation:**
   - Prefer a subscription model via Google Play over one-time payments for sustainability.
   - Integrate with Google Play Billing Library (com.android.billingclient:billing:7.0.0).
   - Manage user quotas and premium memberships from the backend.

4. **Security and Play Compliance:**
   - Apply strict Proguard rules to obfuscate API calls, keys, and sensitive information.
   - Ensure compliance with Play Store data policies and testing phases (Internal Testing, Beta).

5. **Configuration Files and Code:**
   - Abstract API calls within a network package.
   - Align configurations with MainActivity or ViewModel structures.
   - Optimize Gradle and Proguard rule files for enhanced security and performance.

This setup ensures the privacy of your API key, prevents misuse, supports a subscription-based revenue model, and adheres to Google Play's highest standards. Ensure your backend proxy is scalable and reliable.
AutomationAndroidMobile Development+3
B@bariskarakaya5534
0
Secondhand Item Resale Listing Builder (JSON)
Text

Turn notes and photo descriptions of a used item into a strict JSON resale package: honest condition grade with every defect disclosed, evidence-based quick sale, list and floor prices, a title and description, photo checklist, buyer FAQ, negotiation plan, and safe handover steps.

1{
2 "role": "Experienced secondhand marketplace seller who writes honest, fast-selling listings and prices used items from real evidence",
3 "task": "Turn my notes and photo descriptions of one used item into a complete, honest resale listing package as a single strict JSON object: condition grade, pricing with reasoning, a title and description ready for marketplaces, photo checklist, buyer FAQ, negotiation plan, and safe handover steps.",
4 "context": {
5 "item": "${item:standing desk with electric height adjustment}",
6 "brand_and_model": "${brand_model:unknown brand, about 140 x 70 cm top}",
7 "age_and_usage": "${age_usage:bought three years ago, used daily in a home office}",
8 "seller_notes": "${notes:small scratch on the front edge, one motor makes a light hum, original manual lost}",
9 "photo_descriptions": "${photos:front view, top surface close-up, control panel, legs at full height}",
10 "original_price": "${original_price:450 EUR}",
...+122 more lines
PricingSalesJSON+2
F@f
0
Garage Sale Plan Builder (YAML)
Text

Turn a list of things to sell into a YAML garage sale plan: sorting rules, a quick-sale pricing guide with bundles, a prep timeline, table layout, sign and listing text, cash and payment setup, roles, a day-of schedule, haggling replies, safety, and a plan for unsold items.

1role: Organized, upbeat garage sale planner who helps households clear clutter and earn a fair amount in one well-run day
2task: >
3 Turn my notes about the items I want to sell, my space, and my date into a complete garage sale
4 plan as YAML: a sorting and pricing guide, a prep timeline, a layout of the selling area,
5 signs and listing text, a cash and payment setup, a day-of schedule with roles, haggling rules,
6 safety reminders, and a plan for everything that does not sell.
7
8inputs:
9 sale_date_and_hours: ${date:Saturday, 08:00 to 13:00}
10 location: ${location:driveway and open garage of a house on a quiet residential street}
...+83 more lines
PlanningOrganizationPricing+2
F@f
0