### NativePHP Project Listing Format Reference (Markdown)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

This markdown provides a standardized format for all project entries in the NativePHP awesome list. It specifies the required fields: Project Name, GitHub URL, a single-paragraph description, project Type, and comma-separated Tags.

```markdown
### Project Name (Title Case)
https://github.com/username/repository-name

A single paragraph description that clearly explains what the project does,
its main features, and its primary use case. Keep it concise but informative.

Type: [electron | tauri | mobile]

Tags: max, five, comma, separated, terms

---
```

--------------------------------

### Submit NativePHP Project Listing via Git (Bash)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

This bash script outlines the process for contributing a new NativePHP project to the repository. It involves forking, cloning, creating a new branch, editing the README.md with the project details in the correct format, committing, and pushing the changes to create a pull request.

```bash
# Fork and clone the repository
git clone https://github.com/nativephp-community/awesome-nativephp.git
cd awesome-nativephp

# Create a new branch
git checkout -b add-my-project

# Edit README.md and add your project in alphabetical order
# Follow the format exactly as shown in the example

# Example addition to README.md under "Apps & Games" section:
# ### My Awesome App
# https://github.com/username/my-awesome-app
#
# A desktop application for managing your daily tasks with calendar integration.
#
# Type: electron
#
# Tags: productivity, tasks, calendar, desktop, open-source
#
# ---

# Commit your changes
git add README.md
git commit -m "Add My Awesome App"

# Push to your fork
git push origin add-my-project

# Create a pull request on GitHub
# Important: Only submit ONE listing per PR
# Place your listing alphabetically within its section
# Do not move or modify other listings
```

--------------------------------

### Add NativePHP Project to List (Markdown)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

This markdown format is used to add a new NativePHP project to the awesome list. It requires a title, GitHub URL, a concise description, project type (electron, tauri, or mobile), and relevant tags.

```markdown
### Your Project Title
https://github.com/yourusername/your-project

A concise description of what your project does and its main features.

Type: [electron | tauri | mobile]

Tags: tag1, tag2, tag3, tag4, tag5

---
```

--------------------------------

### Search NativePHP Apps by Category (Bash)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

These bash commands use `grep` to search for NativePHP projects based on keywords within their descriptions or tags. They allow users to find applications related to specific functionalities like password management, developer tools, or notification features.

```bash
# Find password managers
grep -i -B 5 -A 3 "password" README.md

# Find developer tools
grep -i -B 5 -A 3 "devtool" README.md

# Find open-source projects
grep -B 5 "open-source" README.md

# Find desktop notification apps
grep -i -B 5 -A 3 "notification" README.md

# Find menubar/taskbar applications
grep -i -B 5 -A 3 "menubar\|taskbar" README.md
```

--------------------------------

### Discover NativePHP Apps by Type (Bash)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

These bash commands utilize `grep` to filter and find NativePHP projects based on their platform type (electron, mobile, tauri) or specific tags within the README.md file. They are useful for local exploration of the repository's contents.

```bash
# Clone the repository to search locally
git clone https://github.com/nativephp-community/awesome-nativephp.git
cd awesome-nativephp

# Find all Electron apps
grep -A 5 "Type: electron" README.md

# Find all mobile apps
grep -A 5 "Type: mobile" README.md

# Find all Tauri apps
grep -A 5 "Type: tauri" README.md

# Search for specific tags (e.g., productivity apps)
grep -B 3 "productivity" README.md

# Count total number of apps
grep -c "^### " README.md
```

--------------------------------

### Automated Link Validation with GitHub Actions (YAML)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

This YAML configuration sets up a GitHub Actions workflow that runs daily and on pull requests/pushes to the main branch. It uses the `lycheeverse/lychee-action` to automatically check for broken links within markdown and html files in the repository.

```yaml
# .github/workflows/link-check.yml
name: Broken Link Check
on:
  schedule:
    - cron: '0 0 * * *' # Run daily at midnight
  pull_request:
    branches: [ main ]
  push:
    branches: [ main ]

jobs:
  check-links:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Check for broken links
        uses: lycheeverse/lychee-action@v1
        with:
          args: --verbose --no-progress './**/*.md' './**/*.html'
```

--------------------------------

### Contribution Validation Rules for NativePHP Projects (Bash)

Source: https://context7.com/nativephp/awesome-nativephp/llms.txt

This bash script outlines the essential validation rules for submitting a new NativePHP project. It emphasizes alphabetical order, single listing per pull request, adherence to the exact format, and inclusion of all required fields (Type, Tags).

```bash
# Before submitting a PR, verify:
# 1. Your listing is in alphabetical order within its section
# 2. You have not moved or modified other existing listings
# 3. Your PR contains only ONE new listing
# 4. Your listing follows the exact format with all required fields

# Example of correct placement (alphabetical):
# ### Air Quality Index Taskbar App  <-	Existing
# ### APNEE                           <-	Existing
# ### My App Name                     <-	Your new listing (alphabetically placed)
# ### Cronikl                         <-	Existing

# Example of INCORRECT (will be rejected):
# - Moving existing entries
# - Adding multiple listings in one PR
# - Using different formatting
# - Missing required fields (Type or Tags)
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.