Skip to content

Commit 90417af

Browse files
asperpharmaasperpharma
authored
Merge branch 'main' into asperpharma-patch-13
2 parents 67f73e1 + 6b6add8 commit 90417af

788 files changed

Lines changed: 679834 additions & 3802 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.github/ISSUE_TEMPLATE/asper-beauty-shop.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: Asper Beauty Shop
3+
about: Describe this issue template's purpose here.
4+
title: ''
5+
labels: ''
6+
assignees: asperpharma
7+
8+
---
9+
10+

‎.github/ISSUE_TEMPLATE/prompt_submission.md‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
name: Prompt Submission
3+
about: Submit a new AI prompt to the Asper Beauty Shop prompt library
4+
title: "[PROMPT] "
5+
labels: prompt-submission
6+
assignees: ''
7+
---
8+
9+
## Prompt Title
10+
<!-- A clear, descriptive title for your prompt -->
11+
12+
## Category
13+
<!-- Select the appropriate category -->
14+
- [ ] ui-design
15+
- [ ] web-development
16+
- [ ] components
17+
- [ ] ux-research
18+
- [ ] animation
19+
- [ ] responsive
20+
- [ ] accessibility
21+
22+
## Difficulty Level
23+
- [ ] Beginner
24+
- [ ] Intermediate
25+
- [ ] Advanced
26+
27+
## Tags
28+
<!-- Add relevant tags, e.g., #react #tailwind #accessibility #shopify -->
29+
30+
## Description
31+
<!-- Briefly describe what this prompt does and when to use it -->
32+
33+
## The Prompt
34+
<!-- Paste the full prompt text here -->
35+
36+
```
37+
[Your prompt here]
38+
```
39+
40+
## Example Usage
41+
<!-- Show how to use this prompt with a real-world example input -->
42+
43+
**Input:**
44+
45+
**Expected Output:**
46+
47+
## Sample Results
48+
<!-- Optionally include a sample of what the prompt produces -->
49+
50+
## Brand Alignment (Asper-Specific)
51+
<!-- Does this prompt enforce the "Ivory & Gold" design system? -->
52+
- [ ] Uses Soft Ivory (#F8F8FF), Maroon (#800020), Shiny Gold (#C5A028)
53+
- [ ] Enforces Playfair Display / Montserrat / Tajawal typography
54+
- [ ] Supports RTL (Arabic) localization
55+
- [ ] Follows "Clinical Luxury" / "Morning Spa" aesthetic
56+
- [ ] N/A — general-purpose prompt
57+
58+
## Checklist
59+
- [ ] Prompt follows the established format
60+
- [ ] Includes a clear description
61+
- [ ] Contains example usage
62+
- [ ] Has appropriate tags
63+
- [ ] Tested with Claude (or equivalent AI)
64+
- [ ] Frontend/UI focused content
65+
- [ ] No duplicate of existing prompts

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
## Description
2+
<!-- Briefly describe what this PR adds or changes. -->
3+
4+
## Type of Change
5+
- [ ] 🆕 New prompt addition
6+
- [ ] 🔧 Prompt improvement/fix
7+
- [ ] 🎨 UI component (React/Tailwind)
8+
- [ ] 🧪 Feature implementation
9+
- [ ] 📋 Documentation update
10+
- [ ] 🗂️ Category organization
11+
- [ ] 🐛 Bug fix
12+
- [ ] 🔒 Security fix
13+
- [ ] Other: ___________
14+
15+
## Category
16+
<!-- Which category does this affect? -->
17+
- [ ] ui-design
18+
- [ ] web-development
19+
- [ ] components
20+
- [ ] ux-research
21+
- [ ] animation
22+
- [ ] responsive
23+
- [ ] accessibility
24+
- [ ] src/ (codebase change)
25+
- [ ] supabase/ (backend change)
26+
27+
## Brand Alignment (for UI/component changes)
28+
<!-- Does this change maintain the "Clinical Luxury" brand DNA? -->
29+
- [ ] Uses Soft Ivory (#F8F8FF) as the background canvas
30+
- [ ] Uses Deep Maroon (#800020) for primary actions and headers
31+
- [ ] Uses Shiny Gold (#C5A028) for 1px borders and hover states (the "Gold Stitch")
32+
- [ ] Uses Dark Charcoal (#333333) for body text
33+
- [ ] Supports RTL layout for Arabic localization
34+
- [ ] N/A — no visual changes
35+
36+
## Checklist
37+
38+
### For New Prompts
39+
- [ ] Prompt follows the established format (YAML frontmatter + sections)
40+
- [ ] Includes clear description
41+
- [ ] Contains example usage
42+
- [ ] Provides sample output (if applicable)
43+
- [ ] Has appropriate tags
44+
- [ ] Tested with Claude
45+
- [ ] Placed in correct category directory
46+
- [ ] Frontend-focused content
47+
48+
### For Code Changes
49+
- [ ] `npm run lint` passes with 0 errors
50+
- [ ] `npm run build` completes without errors
51+
- [ ] RTL (Arabic) layout is not broken
52+
- [ ] Mobile responsive on all breakpoints
53+
- [ ] Tailwind uses semantic tokens (not raw hex values)
54+
55+
### For All Contributions
56+
- [ ] Clear and understandable content
57+
- [ ] No spelling or grammar errors
58+
- [ ] Follows contribution guidelines
59+
- [ ] No duplicate content
60+
- [ ] No sensitive credentials or API keys committed
61+
62+
## Testing
63+
- [ ] I have tested this locally
64+
- [ ] The changes produce consistent, expected results
65+
- [ ] The examples work as described (for prompts)
66+
- [ ] Verified on mobile viewport
67+
68+
## Additional Notes
69+
<!-- Add any additional context, screenshots, or information about your changes here. -->
70+
71+
<!-- closes #[issue-number] -->

‎.github/workflows/azure-functions-app-nodejs.yml‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
# This workflow will build a Node.js project and deploy it to an Azure Functions App on Windows or Linux when a commit is pushed to your default branch.
2+
#
3+
# This workflow assumes you have already created the target Azure Functions app.
4+
# For instructions see:
5+
# - https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-node
6+
# - https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-typescript
7+
#
8+
# To configure this workflow:
9+
# 1. Set up the following secrets in your repository:
10+
# - AZURE_FUNCTIONAPP_PUBLISH_PROFILE
11+
# 2. Change env variables for your configuration.
12+
#
13+
# For more information on:
14+
# - GitHub Actions for Azure: https://github.com/Azure/Actions
15+
# - Azure Functions Action: https://github.com/Azure/functions-action
16+
# - Publish Profile: https://github.com/Azure/functions-action#using-publish-profile-as-deployment-credential-recommended
17+
# - Azure Service Principal for RBAC: https://github.com/Azure/functions-action#using-azure-service-principal-for-rbac-as-deployment-credential
18+
#
19+
# For more samples to get started with GitHub Action workflows to deploy to Azure: https://github.com/Azure/actions-workflow-samples/tree/master/FunctionApp
20+
21+
name: Deploy Node.js project to Azure Function App
22+
23+
on:
24+
push:
25+
branches: ["main"]
26+
27+
env:
28+
AZURE_FUNCTIONAPP_NAME: 'your-app-name' # set this to your function app name on Azure
29+
AZURE_FUNCTIONAPP_PACKAGE_PATH: '.' # set this to the path to your function app project, defaults to the repository root
30+
NODE_VERSION: '20.x' # set this to the node version to use (e.g. '8.x', '10.x', '12.x')
31+
32+
jobs:
33+
build-and-deploy:
34+
runs-on: windows-latest # For Linux, use ubuntu-latest
35+
environment: dev
36+
steps:
37+
- name: 'Checkout GitHub Action'
38+
uses: actions/checkout@v4
39+
40+
# If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below
41+
# - name: 'Login via Azure CLI'
42+
# uses: azure/login@v1
43+
# with:
44+
# creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository
45+
46+
- name: Setup Node ${{ env.NODE_VERSION }} Environment
47+
uses: actions/setup-node@v4
48+
with:
49+
node-version: ${{ env.NODE_VERSION }}
50+
51+
- name: 'Resolve Project Dependencies Using Npm'
52+
shell: pwsh # For Linux, use bash
53+
run: |
54+
pushd './${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}'
55+
npm install
56+
npm run build --if-present
57+
npm run test --if-present
58+
popd
59+
60+
- name: 'Run Azure Functions Action'
61+
uses: Azure/functions-action@v1
62+
id: fa
63+
with:
64+
app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }}
65+
package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}
66+
publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC

‎.github/workflows/azure-staticwebapp.yml‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# This workflow will build and push a web application to an Azure Static Web App when you change your code.
2+
#
3+
# This workflow assumes you have already created the target Azure Static Web App.
4+
# For instructions see https://docs.microsoft.com/azure/static-web-apps/get-started-portal?tabs=vanilla-javascript
5+
#
6+
# To configure this workflow:
7+
#
8+
# 1. Set up a secret in your repository named AZURE_STATIC_WEB_APPS_API_TOKEN with the value of your Static Web Apps deployment token.
9+
# For instructions on obtaining the deployment token see: https://docs.microsoft.com/azure/static-web-apps/deployment-token-management
10+
#
11+
# 3. Change the values for the APP_LOCATION, API_LOCATION and APP_ARTIFACT_LOCATION, AZURE_STATIC_WEB_APPS_API_TOKEN environment variables (below).
12+
# For instructions on setting up the appropriate configuration values go to https://docs.microsoft.com/azure/static-web-apps/front-end-frameworks
13+
name: Deploy web app to Azure Static Web Apps
14+
15+
on:
16+
push:
17+
branches: [ "main" ]
18+
pull_request:
19+
types: [opened, synchronize, reopened, closed]
20+
branches: [ "main" ]
21+
22+
# Environment variables available to all jobs and steps in this workflow
23+
env:
24+
APP_LOCATION: "/" # location of your client code
25+
API_LOCATION: "api" # location of your api source code - optional
26+
APP_ARTIFACT_LOCATION: "build" # location of client code build output
27+
AZURE_STATIC_WEB_APPS_API_TOKEN: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }} # secret containing deployment token for your static web app
28+
29+
permissions:
30+
contents: read
31+
32+
jobs:
33+
build_and_deploy_job:
34+
permissions:
35+
contents: read # for actions/checkout to fetch code
36+
pull-requests: write # for Azure/static-web-apps-deploy to comment on PRs
37+
if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed')
38+
runs-on: ubuntu-latest
39+
name: Build and Deploy Job
40+
steps:
41+
- uses: actions/checkout@v4
42+
with:
43+
submodules: true
44+
- name: Build And Deploy
45+
id: builddeploy
46+
uses: Azure/static-web-apps-deploy@v1
47+
with:
48+
azure_static_web_apps_api_token: ${{ env.AZURE_STATIC_WEB_APPS_API_TOKEN }} # secret containing api token for app
49+
repo_token: ${{ secrets.GITHUB_TOKEN }} # Used for Github integrations (i.e. PR comments)
50+
action: "upload"
51+
###### Repository/Build Configurations - These values can be configured to match you app requirements. ######
52+
# For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig
53+
app_location: ${{ env.APP_LOCATION }}
54+
api_location: ${{ env.API_LOCATION }}
55+
app_artifact_location: ${{ env.APP_ARTIFACT_LOCATION }}
56+
###### End of Repository/Build Configurations ######
57+
58+
close_pull_request_job:
59+
permissions:
60+
contents: none
61+
if: github.event_name == 'pull_request' && github.event.action == 'closed'
62+
runs-on: ubuntu-latest
63+
name: Close Pull Request Job
64+
steps:
65+
- name: Close Pull Request
66+
id: closepullrequest
67+
uses: Azure/static-web-apps-deploy@v1
68+
with:
69+
azure_static_web_apps_api_token: ${{ env.AZURE_STATIC_WEB_APPS_API_TOKEN }} # secret containing api token for app
70+
action: "close"

‎.github/workflows/azure-webapps-node.yml‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
# This workflow will build and push a node.js application to an Azure Web App when a commit is pushed to your default branch.
2+
#
3+
# This workflow assumes you have already created the target Azure App Service web app.
4+
# For instructions see https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs?tabs=linux&pivots=development-environment-cli
5+
#
6+
# To configure this workflow:
7+
#
8+
# 1. Download the Publish Profile for your Azure Web App. You can download this file from the Overview page of your Web App in the Azure Portal.
9+
# For more information: https://docs.microsoft.com/en-us/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials
10+
#
11+
# 2. Create a secret in your repository named AZURE_WEBAPP_PUBLISH_PROFILE, paste the publish profile contents as the value of the secret.
12+
# For instructions on obtaining the publish profile see: https://docs.microsoft.com/azure/app-service/deploy-github-actions#configure-the-github-secret
13+
#
14+
# 3. Change the value for the AZURE_WEBAPP_NAME. Optionally, change the AZURE_WEBAPP_PACKAGE_PATH and NODE_VERSION environment variables below.
15+
#
16+
# For more information on GitHub Actions for Azure: https://github.com/Azure/Actions
17+
# For more information on the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
18+
# For more samples to get started with GitHub Action workflows to deploy to Azure: https://github.com/Azure/actions-workflow-samples
19+
20+
on:
21+
push:
22+
branches: [ "main" ]
23+
workflow_dispatch:
24+
25+
env:
26+
AZURE_WEBAPP_NAME: your-app-name # set this to your application's name
27+
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
28+
NODE_VERSION: '20.x' # set this to the node version to use
29+
30+
permissions:
31+
contents: read
32+
33+
jobs:
34+
build:
35+
runs-on: ubuntu-latest
36+
steps:
37+
- uses: actions/checkout@v4
38+
39+
- name: Set up Node.js
40+
uses: actions/setup-node@v4
41+
with:
42+
node-version: ${{ env.NODE_VERSION }}
43+
cache: 'npm'
44+
45+
- name: npm install, build, and test
46+
run: |
47+
npm install
48+
npm run build --if-present
49+
npm run test --if-present
50+
51+
- name: Upload artifact for deployment job
52+
uses: actions/upload-artifact@v4
53+
with:
54+
name: node-app
55+
path: .
56+
57+
deploy:
58+
permissions:
59+
contents: none
60+
runs-on: ubuntu-latest
61+
needs: build
62+
environment:
63+
name: 'Development'
64+
url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}
65+
66+
steps:
67+
- name: Download artifact from build job
68+
uses: actions/download-artifact@v4
69+
with:
70+
name: node-app
71+
72+
- name: 'Deploy to Azure WebApp'
73+
id: deploy-to-webapp
74+
uses: azure/webapps-deploy@v2
75+
with:
76+
app-name: ${{ env.AZURE_WEBAPP_NAME }}
77+
publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}
78+
package: ${{ env.AZURE_WEBAPP_PACKAGE_PATH }}

0 commit comments

Comments
 (0)